Systems and methods for creating and using equipment definitions

ABSTRACT

Systems and methods for creating and using equipment definitions are provided. An archetypal device used to identify one or more data points associated with the archetypal device. A point definition is generated for each identified data point associated with the archetypal device. Each point definition includes an abstraction of a text string extracted from the corresponding data point that is applicable to multiple different devices of the same type of building equipment. The generated point definitions are used to create an equipment definition for a type of building equipment. The equipment definition can be used to identify data points associated with other devices of the same type of building equipment and to automatically create equipment objects representing such devices.

CROSS-REFERENCE TO RELATED PATENT APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.15/592,031 filed May 10, 2017, now U.S. Pat. No. 10,558,183, which is acontinuation of U.S. patent application Ser. No. 14/251,414 filed Apr.11, 2014, now U.S. Pat. No. 9,703,276, the entire disclosures of whichare incorporated by reference herein.

BACKGROUND

The present disclosure relates generally to the field of buildingautomation systems. The present disclosure relates more particularly tosystems and methods for creating and using equipment definitions forbuilding equipment in a building automation system.

A building automation system (BAS) is, in general, a system of devicesconfigured to control, monitor, and manage equipment in or around abuilding or building area. A BAS can include a heating, ventilation, andair conditioning (HVAC) system, a security system, a lighting system, afire alerting system, another system that is capable of managingbuilding functions or devices, or any combination thereof. BAS devicesmay be installed in any environment (e.g., an indoor area or an outdoorarea) and the environment may include any number of buildings, spaces,zones, rooms, or areas. A BAS may include METASYS building controllersor other devices sold by Johnson Controls, Inc., as well as buildingdevices and components from other sources.

A BAS may include one or more computer systems (e.g., servers, BAScontrollers, etc.) that serve as enterprise level controllers,application or data servers, head nodes, master controllers, or fieldcontrollers for the BAS. Such computer systems may communicate withmultiple downstream building systems or subsystems (e.g., an HVACsystem, a security system, etc.) according to like or disparateprotocols (e.g., LON, BACnet, etc.). The computer systems may alsoprovide one or more human-machine interfaces or client interfaces (e.g.,graphical user interfaces, reporting interfaces, text-based computerinterfaces, client-facing web services, web servers that provide pagesto web clients, etc.) for controlling, viewing, or otherwise interactingwith the BAS, its subsystems, and devices.

SUMMARY

One implementation of the present disclosure is a method for creating anequipment definition for a type of building equipment in a buildingautomation system. The method includes operating an archetypal device ofthe type of building equipment to affect a variable state or conditionwithin a building and identifying one or more data points associatedwith the archetypal device. Each of the identified data points includesa text string specific to the archetypal device. The method includesautomatically creating, for each of the identified data points, anabstraction of the text string specific to the archetypal device. Theabstraction of the text string includes a portion of the text stringthat is applicable to multiple different devices of the same type ofbuilding equipment. The method includes generating a point definitionfor each identified data point associated with the archetypal device.Each point definition includes the abstraction of the text string of thecorresponding data point. The method includes using the generated pointdefinitions to create an equipment definition for the type of buildingequipment. The equipment definition includes one or more of thegenerated point definitions.

In some embodiments, the method includes using the stored equipmentdefinition to automatically identify one or more data points associatedwith a second device of the same type of building equipment andautomatically mapping the identified data points of the second device toan equipment object representing the second device.

In some embodiments, the method includes providing a user interface to aclient device. The user interface may include a display of one or moredevices of the building automation system. The method may includereceiving a user selection of the archetypal device via the userinterface.

In some embodiments, each point definition includes a criterion foridentifying a data point associated with a second device of the sametype of building equipment of the building automation system. In someembodiments, the criterion for identifying the data point associatedwith the second device includes at least one of an instance number ofthe data point, a network address of the data point, or a network pointtype of the data point. In some embodiments, the criterion foridentifying the data point associated with the second device includesthe abstraction of the text string of the corresponding data point ofthe archetypal device.

In some embodiments, the method includes providing a user interface forvisualizing the equipment definition to a client device. The userinterface may include a point definition portion having a display of thegenerated point definitions, a user input portion configured to receivea user selection of one or more of the point definitions displayed inthe point definition portion, and a display data portion having anindication of an abstracted data point corresponding to each of thepoint definitions selected via the user input portion.

In some embodiments, the method includes receiving a user selection ofone or more of the point definitions and automatically mapping one ormore data points of a second device that satisfy the selected pointdefinitions to a user interface for visualizing data associated with thesecond device.

In some embodiments, the method includes associating the equipmentdefinition with a category of building equipment and using the equipmentdefinition to filter building equipment of the building automationsystem by the category associated with the equipment definition.

Another implementation of the present disclosure is a method forcreating and using an equipment object representing building equipmentof a building automation system. The method includes obtaining anequipment definition for a type of building equipment. The equipmentdefinition includes one or more point definitions, each point definitionincluding an abstraction of a text string extracted from a data pointassociated with an archetypal device of the type of building equipment.The method includes identifying a second device of the buildingautomation system of the same type as the archetypal device, using theequipment definition to automatically identify one or more data pointsassociated with the second device that satisfy one or more of the pointdefinitions, automatically mapping the identified data points of thesecond device to an equipment object representing the second device, andusing the equipment object to monitor and control the second device toaffect a variable state or condition within a building.

In some embodiments, each point definition includes a criterion foridentifying a data point associated with the second device. In someembodiments, the criterion for identifying the data point associatedwith the second device comprises at least one of an instance number ofthe data point, a network address of the data point, or a network pointtype of the data point. In some embodiments, the criterion foridentifying the data point associated with the second device includesthe abstraction of the text string of the corresponding data point ofthe archetypal device. In some embodiments, the criterion foridentifying the data point associated with the second device includesdevice specific information (e.g., MAC address, IP address, networkaddress, etc.).

In some embodiments, using the equipment definition to identify one ormore data points associated with the second device includes extracting asearch criterion from each point definition of the equipment definition,accessing a network of the building automation system to determine oneor more data points associated with the second device, using theextracted search criterion to search the data points of the seconddevice for a data point that satisfies the search criterion, andidentifying the data point that satisfies the search criterion as a datapoint associated with the second device that satisfies one or more ofthe point definitions.

In some embodiments, automatically mapping the identified data points ofthe second device to the equipment object includes determining a networkaddress for each identified data point of the second device and mappingthe network address for each identified data point of the second deviceto the equipment object representing the second device.

In some embodiments, determining a network address for each identifieddata point of the second device includes accessing a data point networkfor the building automation system and using the data point network toidentify an existing relationship between the network address and anidentified data point of the second device.

In some embodiments, the method includes using the equipment definitionto automatically identify, by the processing circuit, one or more of thepoint definitions indicated as display data. In some embodiments, theprocessing circuit maps a data point of the second device to anequipment object representing the second device in response to adetermination that the data point satisfies one or more of the pointdefinitions to an equipment object. In some embodiments, the methodincludes creating a display object for display via a user interface andautomatically mapping a data point of the second device to the displayobject in response to a determination that the data point satisfies oneor more of the point definitions indicated as display data. The displayobject may include a subset of the data points of the correspondingequipment object. In some embodiments, the method includes providing auser interface to a client device. The user interface may include adisplay of the one or more data points mapped to the display object.

Another implementation of the present disclosure is a method forproviding a display of data points associated with building equipment ofa building automation system. The method includes obtaining an equipmentdefinition for a type of building equipment. The equipment definitionincludes one or more point definitions and an indication of whether eachpoint definition is identified as display data. Each point definitionincludes an abstraction of a text string extracted from a data pointassociated with an archetypal device of the type of building equipment.The method includes using the equipment definition to automaticallyidentify one or more data points that satisfy one or more of the pointdefinitions identified as display data and are associated with a seconddevice of the same type of building equipment, automatically mapping theidentified data points to a display object, and generating a userinterface for display on a client device. The user interface includes adisplay of the one or more data points mapped to the display object. Themethod further includes using the display object to monitor and controlthe second device to affect a variable state or condition within abuilding.

In some embodiments, each point definition includes a search criterionfor identifying a data point associated with the device. The searchcriterion may include the abstraction of the text string of thecorresponding data point of the archetypal device.

Those skilled in the art will appreciate that the summary isillustrative only and is not intended to be in any way limiting. Otheraspects, inventive features, and advantages of the devices and/orprocesses described herein, as defined solely by the claims, will becomeapparent in the detailed description set forth herein and taken inconjunction with the accompanying drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a perspective view drawing of a building equipped with abuilding automation system (BAS), according to an exemplary embodiment.

FIG. 2 is a block diagram illustrating the BAS of FIG. 1 in greaterdetail, showing a BAS controller in communication with several BASsubsystems and a plurality of BAS devices, according to an exemplaryembodiment.

FIG. 3 is a block diagram illustrating the BAS controller of FIG. 2 ingreater detail, according to an exemplary embodiment.

FIG. 4 is a block diagram illustrating logical relationships between theBAS controller of FIG. 2, a data points network, BAS equipment, and anequipment definition referenced by the BAS equipment, according to anexemplary embodiment.

FIG. 5 is a drawing of a user interface for initiating the creation ofbuilding objects representing buildings and spaces within buildings,according to an exemplary embodiment.

FIG. 6 is a drawing of a user interface for creating and viewingbuilding objects and defining relationships between building objects,according to an exemplary embodiment.

FIG. 7 is a drawing illustrating a technique for creating buildingobjects representing rooms wherein folders with the names of the roomsto be created are dragged and dropped into the user interface of FIG. 6,according to an exemplary embodiment.

FIG. 8 is a drawing illustrating another technique for creating buildingobjects wherein building object data is imported from a table or otherdata source, according to an exemplary embodiment.

FIG. 9 is a drawing of a user interface for creating an equipmentdefinition and defining attributes of building equipment that referencesthe equipment definition, according to an exemplary embodiment.

FIG. 10 is a drawing of a data points network that defines the datapoints associated with various BAS devices, according to an exemplaryembodiment.

FIG. 11 is a drawing illustrating attributes of various data pointsprovided by the data points network of FIG. 10, according to anexemplary embodiment.

FIG. 12 is a drawing of a user interface for viewing an equipmentdefinition including a plurality of point definitions, search criteriaassociated with each point definition, and a display data portionidentifying one or more of the defined data points to display, accordingto an exemplary embodiment.

FIGS. 13-14 are block diagrams illustrating the applicability ofequipment definitions to many different BAS devices of the same generaltype, according to an exemplary embodiment.

FIG. 15 is a drawing of a user interface for initiating the creation ofequipment objects representing BAS devices based on a selected equipmentdefinition, according to an exemplary embodiment.

FIG. 16 is a drawing of an equipment discovery table used in thecreation of equipment objects, each column of the equipment discoverytable corresponding to a point definition of the selected equipmentdefinition, according to an exemplary embodiment.

FIG. 17 is a drawing of a BAS network tree defining various BAS devicesthat exist within the BAS, according to an exemplary embodiment.

FIG. 18 is a drawing of the equipment discovery table of FIG. 16automatically populated with data points associated with various BASdevices defined by the BAS network tree and identified using theselected equipment definition, according to an exemplary embodiment.

FIGS. 19-21 are drawings illustrating an equipment object created usingthe equipment discovery table of FIG. 16, the equipment object havingattributes defined by the point definitions of the selected equipmentdefinition and mapped to various data points identified using theselected equipment definition, according to an exemplary embodiment.

FIG. 22 is a flowchart illustrating an iterative process for using anequipment definition to identify data points of various BAS devices andmapping the identified data points to an equipment object, according toan exemplary embodiment.

FIGS. 23-24 are drawings illustrating a user interface for visualizingthe data points mapped to an equipment object, according to an exemplaryembodiment.

FIGS. 25-26 are drawings illustrating a user interface for associatingequipment objects with each other and with building objects, accordingto an exemplary embodiment.

FIGS. 27-32 are drawings of user interfaces for visualizing data pointsassociated with various equipment objects and/or building objects,according to an exemplary embodiment.

FIG. 33 is a drawing of one of the user interfaces of FIGS. 27-32displayed via a client device such as a computer terminal, according toan exemplary embodiment.

FIGS. 34-35 are drawings of the user interface of FIG. 33 displayed viaa mobile device such as a smartphone, according to an exemplaryembodiment.

FIG. 36 is a flowchart of a process for creating an equipment definitionfor a type of building equipment in a building automation system,according to an exemplary embodiment.

FIG. 37 is a flowchart of a process for using an equipment definition tocreate an equipment object representing building equipment of a buildingautomation system, according to an exemplary embodiment.

FIG. 38 is a flowchart of a process for providing a display of datapoints associated with building equipment of a building automationsystem, according to an exemplary embodiment.

FIG. 39 is a drawing of a user interface for visualizing “served by”relationships between building equipment and other building equipmentand/or spaces, according to an exemplary embodiment.

DETAILED DESCRIPTION

Referring generally to the FIGURES, systems and methods for creating andusing equipment definitions in a building automation system (BAS) areshown, according to various exemplary embodiments. The systems andmethods described herein may be used to generate equipment definitionsfor various types of building equipment. An equipment definition allowsfor the abstraction of equipment data from a physical piece of buildingequipment (e.g., an individual BAS device) so that the equipment datacan be applied to a room or space. In some embodiments, an equipmentdefinition defines various types of data points that are generallyassociated with a particular type of building equipment. For example, anequipment definition for a variable air volume modular assembly (VMA)may specify data point types such as room temperature, damper position,supply air flow, and/or other types data measured or used by the VMA.

Advantageously, an equipment definition specifies data point types asgeneralized types of data without regard to the model, manufacturer,vendor, or other differences between building equipment of the samegeneral type. An equipment definition can be referenced by multipledifferent variants of the same type of building equipment to facilitatethe presentation of data points associated with the building equipment(e.g., via a user interface) in a consistent and user-friendly manner.For example, an equipment definition may specify which data points aredisplayed via a user interface.

Equipment definitions can be automatically created by abstracting thedata points provided by archetypal controllers (e.g., typical orrepresentative controllers) for various types of building equipment. Forexample, an archetypal controller for a particular VMA (i.e., “VMA-20”)may provide data points such as “VMA-20.DPR-POS” (i.e., the damperposition of VMA-20) and “VMA-20.SUP-FLOW” (i.e., the supply air flowrate through VMA-20). Equipment-specific data points can be abstractedso that the data points are generally applicable to other equipment ofthe same type. For example, the equipment-specific data point“VMA-20.DPR-POS” can be abstracted to the data point type “DPR-POS” andthe equipment-specific data point “VMA-20.SUP-FLOW” can be abstracted tothe data point type “SUP-FLOW.” Advantageously, the abstracted datapoint types included in an equipment definition allow the equipmentdefinition to be applied to multiple different variants of the same typeof building equipment (e.g., VMAs from different manufacturers, VMAshaving different models or output data formats, etc.).

In some embodiments, an equipment definition specifies a system type(e.g., HVAC, lighting, security, fire, etc.), a system sub-type (e.g.,terminal units, air handlers, central plants), and/or data category(e.g., critical, diagnostic, operational) associated with the buildingequipment to which the definition applies. Building equipment can befiltered by various attributes provided in the equipment definition tofacilitate the reporting and management of equipment data from multiplebuilding systems.

Equipment definitions can be used to automatically map data pointsassociated with building equipment to equipment objects (e.g., softwaredefined objects) representing the building equipment and/or buildingobjects representing building zones (e.g., rooms or spaces). Forexample, an equipment definition may include one or more pointdefinitions. Each point definition may define a data point of aparticular type and may include search criteria for automaticallydiscovering and identifying data points that satisfy the pointdefinition. An equipment definition can be applied to multiple pieces ofbuilding equipment of the same general type (e.g., multiple differentVMA controllers). For example, when an equipment definition is appliedto a second VMA controller (e.g., a VMA controller other than thearchetypal controller used to generate the equipment definition), thesearch criteria provided by the point definitions can be used toautomatically identify data points provided by the second VMA controllerthat satisfy each point definition. The identified data points can beautomatically mapped to a building object or an equipment object.

In some embodiments, the identified data points can be presented in aconsistent and user-friendly manner. For example, the identified datapoints can be displayed via a user interface using user-friendly labelsassociated with each point definition (e.g., “Supply Air Temperature”)rather than equipment-specific labels that are more difficult tounderstand (e.g., “VMA-20.SUP-T”). Equipment objects can be associatedwith each other (e.g., via causal relationships) and/or with buildingobjects (e.g., objects representing building zones) to facilitatevarious monitoring and control operations performed by the BAS.

In some embodiments, a user interface is provided for automaticallycreating equipment definitions and using equipment definitions toautomatically create equipment objects and building objects.Advantageously, equipment definitions can be created in an automatedmanner by abstracting the data points provided by an archetypal BASdevice of a particular type (e.g., an archetypal controller). Forexample, a user can select (via the user interface) an archetypalcontroller for building equipment of a particular type and/or datapoints associated with the archetypal controller to automatically createan equipment definition based on the archetypal controller. Othercontrollers of the same general type can be selected via the userinterface to automatically map data points associated with the othercontrollers to equipment objects based on the search criteria includedin the equipment definition.

Referring now to FIG. 1, a perspective view of a building 10 is shown,according to an exemplary embodiment. A BAS serves building 10. The BASfor building 10 may include any number or type of devices that servebuilding 10. For example, each floor may include one or more securitydevices, video surveillance cameras, fire detectors, smoke detectors,lighting systems, HVAC systems, or other building systems or devices. Inmodern BASs, BAS devices can exist on different networks within thebuilding (e.g., one or more wireless networks, one or more wirednetworks, etc.) and yet serve the same building space or control loop.For example, BAS devices may be connected to different communicationsnetworks or field controllers even if the devices serve the same area(e.g., floor, conference room, building zone, tenant area, etc.) orpurpose (e.g., security, ventilation, cooling, heating, etc.).

BAS devices may collectively or individually be referred to as buildingequipment. Building equipment may include any number or type of BASdevices within or around building 10. For example, building equipmentmay include controllers, chillers, rooftop units, fire and securitysystems, elevator systems, thermostats, lighting, serviceable equipment(e.g., vending machines), and/or any other type of equipment that can beused to control, automate, or otherwise contribute to an environment,state, or condition of building 10. The terms “BAS devices,” “BASdevice” and “building equipment” are used interchangeably throughoutthis disclosure.

Referring now to FIG. 2, a block diagram of a BAS 11 for building 10 isshown, according to an exemplary embodiment. BAS 11 is shown to includea plurality of BAS subsystems 20-26. Each BAS subsystem 20-26 isconnected to a plurality of BAS devices and makes data points forvarying connected devices available to upstream BAS controller 12.Additionally, BAS subsystems 20-26 may encompass other lower-levelsubsystems. For example, an HVAC system may be broken down further as“HVAC system A,” “HVAC system B,” etc. In some buildings, multiple HVACsystems or subsystems may exist in parallel and may not be a part of thesame HVAC system 20.

As shown in FIG. 2, BAS 11 may include a HVAC system 20. HVAC system 20may control HVAC operations building 10. HVAC system 20 is shown toinclude a lower-level HVAC system 42 (named “HVAC system A”). HVACsystem 42 may control HVAC operations for a specific floor or zone ofbuilding 10. HVAC system 42 may be connected to air handling units(AHUs) 32, 34 (named “AHU A” and “AHU B,” respectively, in BAS 11). AHU32 may serve variable air volume (VAV) boxes 38, 40 (named “VAV_3” and“VAV_4” in BAS 11). Likewise, AHU 34 may serve VAV boxes 36 and 110(named “VAV_2” and “VAV_1”). HVAC system 42 may also include chiller 30(named “Chiller A” in BAS 11). Chiller 30 may provide chilled fluid toAHU 32 and/or to AHU 34. HVAC system 42 may receive data (i.e., BASinputs such as temperature sensor readings, damper positions,temperature setpoints, etc.) from AHUs 32, 34. HVAC system 42 mayprovide such BAS inputs to HVAC system 20 and on to middleware 14 andBAS controller 12. Similarly, other BAS subsystems may receive inputsfrom other building devices or objects and provide the received inputsto BAS controller 12 (e.g., via middleware 14).

Middleware 14 may include services that allow interoperablecommunication to, from, or between disparate BAS subsystems 20-26 of BAS11 (e.g., HVAC systems from different manufacturers, HVAC systems thatcommunicate according to different protocols, security/fire systems, ITresources, door access systems, etc.). Middleware 14 may be, forexample, an EnNet server sold by Johnson Controls, Inc. While middleware14 is shown as separate from BAS controller 12, middleware 14 and BAScontroller 12 may integrated in some embodiments. For example,middleware 14 may be a part of BAS controller 12.

Still referring to FIG. 2, window control system 22 may receive shadecontrol information from one or more shade controls, ambient light levelinformation from one or more light sensors, and/or other BAS inputs(e.g., sensor information, setpoint information, current stateinformation, etc.) from downstream devices. Window control system 22 mayinclude window controllers 107, 108 (e.g., named “local windowcontroller A” and “local window controller B,” respectively, in BAS 11).Window controllers 107, 108 control the operation of subsets of windowcontrol system 22. For example, window controller 108 may control windowblind or shade operations for a given room, floor, or building in theBAS.

Lighting system 24 may receive lighting related information from aplurality of downstream light controls (e.g., from room lighting 104).Door access system 26 may receive lock control, motion, state, or otherdoor related information from a plurality of downstream door controls.Door access system 26 is shown to include door access pad 106 (named“Door Access Pad 3F”), which may grant or deny access to a buildingspace (e.g., a floor, a conference room, an office, etc.) based onwhether valid user credentials are scanned or entered (e.g., via akeypad, via a badge-scanning pad, etc.).

BAS subsystems 20-26 may be connected to BAS controller 12 viamiddleware 14 and may be configured to provide BAS controller 12 withBAS inputs from various BAS subsystems 20-26 and their varyingdownstream devices. BAS controller 12 may be configured to makedifferences in building subsystems transparent at the human-machineinterface or client interface level (e.g., for connected or hosted userinterface (UI) clients 16, remote applications 18, etc.). BAS controller12 may be configured to describe or model different building devices andbuilding subsystems using common or unified objects (e.g., softwareobjects stored in memory) to help provide the transparency. Softwareequipment objects may allow developers to write applications capable ofmonitoring and/or controlling various types of building equipmentregardless of equipment-specific variations (e.g., equipment model,equipment manufacturer, equipment version, etc.). Software buildingobjects may allow developers to write applications capable of monitoringand/or controlling building zones on a zone-by-zone level regardless ofthe building subsystem makeup.

Referring now to FIG. 3, a block diagram illustrating a portion of BAS11 in greater detail is shown, according to an exemplary embodiment.Particularly, FIG. 3 illustrates a portion of BAS 11 that services aconference room 102 of building 10 (named “B1_F3_CR5”). Conference room102 may be affected by many different building devices connected to manydifferent BAS subsystems. For example, conference room 102 includes oris otherwise affected by VAV box 110, window controller 108 (e.g., ablind controller), a system of lights 104 (named “Room Lighting 17”),and a door access pad 106.

Each of the building devices shown at the top of FIG. 3 may includelocal control circuitry configured to provide signals to theirsupervisory controllers or more generally to the BAS subsystems 20-26.The local control circuitry of the building devices shown at the top ofFIG. 3 may also be configured to receive and respond to control signals,commands, setpoints, or other data from their supervisory controllers.For example, the local control circuitry of VAV box 110 may includecircuitry that affects an actuator in response to control signalsreceived from a field controller that is a part of HVAC system 20.Window controller 108 may include circuitry that affects windows orblinds in response to control signals received from a field controllerthat is part of window control system (WCS) 22. Room lighting 104 mayinclude circuitry that affects the lighting in response to controlsignals received from a field controller that is part of lighting system24. Access pad 106 may include circuitry that affects door access (e.g.,locking or unlocking the door) in response to control signals receivedfrom a field controller that is part of door access system 26.

Still referring to FIG. 3, BAS controller 12 is shown to include a BASinterface 132 in communication with middleware 14. In some embodiments,BAS interface 132 is a communications interface. For example, BASinterface 132 may include wired or wireless interfaces (e.g., jacks,antennas, transmitters, receivers, transceivers, wire terminals, etc.)for conducting data communications with various systems, devices, ornetworks. BAS interface 132 can include an Ethernet card and port forsending and receiving data via an Ethernet-based communications network.In another example, BAS interface 132 includes a WiFi transceiver forcommunicating via a wireless communications network. BAS interface 132may be configured to communicate via local area networks or wide areanetworks (e.g., the Internet, a building WAN, etc.).

In some embodiments, BAS interface 132 and/or middleware 14 includes anapplication gateway configured to receive input from applicationsrunning on client devices. For example, BAS interface 132 and/ormiddleware 14 may include one or more wireless transceivers (e.g., aWiFitransceiver, a Bluetooth transceiver, a NFC transceiver, a cellulartransceiver, etc.) for communicating with client devices. BAS interface132 may be configured to receive building management inputs frommiddleware 14 or directly from one or more BAS subsystems 20-26. BASinterface 132 and/or middleware 14 can include any number of softwarebuffers, queues, listeners, filters, translators, or othercommunications-supporting services.

Still referring to FIG. 3, BAS controller 12 is shown to include aprocessing circuit 134 including a processor 136 and memory 138.Processor 136 may be a general purpose or specific purpose processor, anapplication specific integrated circuit (ASIC), one or more fieldprogrammable gate arrays (FPGAs), a group of processing components, orother suitable processing components. Processor 136 is configured toexecute computer code or instructions stored in memory 138 or receivedfrom other computer readable media (e.g., CDROM, network storage, aremote server, etc.).

Memory 138 may include one or more devices (e.g., memory units, memorydevices, storage devices, etc.) for storing data and/or computer codefor completing and/or facilitating the various processes described inthe present disclosure. Memory 138 may include random access memory(RAM), read-only memory (ROM), hard drive storage, temporary storage,non-volatile memory, flash memory, optical memory, or any other suitablememory for storing software objects and/or computer instructions. Memory138 may include database components, object code components, scriptcomponents, or any other type of information structure for supportingthe various activities and information structures described in thepresent disclosure. Memory 138 may be communicably connected toprocessor 136 via processing circuit 134 and may include computer codefor executing (e.g., by processor 136) one or more processes describedherein. When processor 136 executes instructions stored in memory 138for completing the various activities described herein, processor 136generally configures BAS controller 12 (and more particularly processingcircuit 134) to complete such activities.

Still referring to FIG. 3, memory 138 is shown to include buildingobjects 142. In some embodiments, BAS controller 12 uses buildingobjects 142 to group otherwise ungrouped or unassociated devices so thatthe group may be addressed or handled by applications together and in aconsistent manner (e.g., a single user interface for controlling all ofthe BAS devices that affect a particular building zone or room).Building objects can apply to spaces of any granularity. For example, abuilding object can represent an entire building, a floor of a building,or individual rooms on each floor. In some embodiments, BAS controller12 creates and/or stores a building object in memory 138 for each zoneor room of building 10. Building objects 142 can be accessed by UIclients 16 and remote applications 18 to provide a comprehensive userinterface for controlling and/or viewing information for a particularbuilding zone. Building objects 142 may be created by building objectcreation module 152 and associated with equipment objects by objectrelationship module 158, described in greater detail below.

Still referring to FIG. 3, memory 138 is shown to include equipmentdefinitions 140. Equipment definitions 140 stores the equipmentdefinitions for various types of building equipment. Each equipmentdefinition may apply to building equipment of a different type. Forexample, equipment definitions 140 may include different equipmentdefinitions for variable air volume modular assemblies (VMAs), fan coilunits, air handling units (AHUs), lighting fixtures, water pumps, and/orother types of building equipment.

Equipment definitions 140 define the types of data points that aregenerally associated with various types of building equipment. Forexample, an equipment definition for VMA may specify data point typessuch as room temperature, damper position, supply air flow, and/or othertypes data measured or used by the VMA. Equipment definitions 140 allowfor the abstraction (e.g., generalization, normalization, broadening,etc.) of equipment data from a specific BAS device so that the equipmentdata can be applied to a room or space.

Each of equipment definitions 140 may include one or more pointdefinitions. Each point definition may define a data point of aparticular type and may include search criteria for automaticallydiscovering and/or identifying data points that satisfy the pointdefinition. An equipment definition can be applied to multiple pieces ofbuilding equipment of the same general type (e.g., multiple differentVMA controllers). When an equipment definition is applied to a BASdevice, the search criteria specified by the point definitions can beused to automatically identify data points provided by the BAS devicethat satisfy each point definition.

In some embodiments, equipment definitions 140 define data point typesas generalized types of data without regard to the model, manufacturer,vendor, or other differences between building equipment of the samegeneral type. The generalized data points defined by equipmentdefinitions 140 allows each equipment definition to be referenced by orapplied to multiple different variants of the same type of buildingequipment.

In some embodiments, equipment definitions 140 facilitate thepresentation of data points in a consistent and user-friendly manner.For example, each equipment definition may define one or more datapoints that are displayed via a user interface. The displayed datapoints may be a subset of the data points defined by the equipmentdefinition.

In some embodiments, equipment definitions 140 specify a system type(e.g., HVAC, lighting, security, fire, etc.), a system sub-type (e.g.,terminal units, air handlers, central plants), and/or data category(e.g., critical, diagnostic, operational) associated with the buildingequipment defined by each equipment definition. Specifying suchattributes of building equipment at the equipment definition levelallows the attributes to be applied to the building equipment along withthe equipment definition when the building equipment is initiallydefined. Building equipment can be filtered by various attributesprovided in the equipment definition to facilitate the reporting andmanagement of equipment data from multiple building systems.

Equipment definitions 140 can be automatically created by abstractingthe data points provided by archetypal controllers (e.g., typical orrepresentative controllers) for various types of building equipment. Insome embodiments, equipment definitions 140 are created by equipmentdefinition module 154, described in greater detail below. An example ofa user interface for visualizing an equipment definition is describedwith reference to FIG. 12.

Still referring to FIG. 3, memory 138 is shown to include equipmentobjects 144. Equipment objects 144 may be software objects that define amapping between a data point type (e.g., supply air temperature, roomtemperature, damper position) and an actual data point (e.g., a measuredor calculated value for the corresponding data point type) for variouspieces of building equipment. Equipment objects 144 may facilitate thepresentation of equipment-specific data points in an intuitive anduser-friendly manner by associating each data point with an attributeidentifying the corresponding data point type. The mapping provided byequipment objects 144 may be used to associate a particular data valuemeasured or calculated by BAS 11 with an attribute that can be displayedvia a user interface.

Equipment objects 144 can be created (e.g., by equipment object creationmodule 156) by referencing equipment definitions 140. For example, anequipment object can be created by applying an equipment definition tothe data points provided by a BAS device. The search criteria includedin an equipment definition can be used to identify data points of thebuilding equipment that satisfy the point definitions. A data point thatsatisfies a point definition can be mapped to an attribute of theequipment object corresponding to the point definition.

Each equipment object may include one or more attributes defined by thepoint definitions of the equipment definition used to create theequipment object. For example, an equipment definition which defines theattributes “Occupied Command,” “Room Temperature,” and “Damper Position”may result in an equipment object being created with the sameattributes. The search criteria provided by the equipment definition areused to identify and map data points associated with a particular BASdevice to the attributes of the equipment object. The creation ofequipment objects is described in greater detail below with reference toequipment object creation module 156. An example of a user interface forcreating equipment objects is described with reference to FIGS. 15-18.

Equipment objects 144 may be related with each other and/or withbuilding objects 142. Causal relationships can be established betweenequipment objects to link equipment objects to each other. For example,a causal relationship can be established between a VMA and an AHU whichprovides airflow to the VMA. Causal relationships can also beestablished between equipment objects 144 and building objects 142. Forexample, equipment objects 144 can be associated with building objects142 representing particular rooms or zones to indicate that theequipment object serves that room or zone. Relationships between objectsare described in greater detail below with reference to objectrelationship module 158. An example of a user interface for establishingrelationships between objects is described with reference to FIGS.25-26.

Still referring to FIG. 3, memory 138 is shown to include clientservices 146 and application services 148. Client services 146 may beconfigured to facilitate interaction and/or communication between BAScontroller 12 and various internal or external clients or applications.For example, client services 146 may include web services or applicationprogramming interfaces available for communication by UI clients 16 andremote applications 18 (e.g., applications running on a mobile device,energy monitoring applications, applications allowing a user to monitorthe performance of the BAS, automated fault detection and diagnosticssystems, etc.). Application services 148 may facilitate direct orindirect communications between remote applications 18, localapplications 150, and BAS controller 12. For example, applicationservices 148 may allow BAS controller 12 to communicate (e.g., over acommunications network) with remote applications 18 running on mobiledevices and/or with other BAS controllers.

In some embodiments, application services 148 facilitate an applicationsgateway for conducting electronic data communications with UI clients 16and/or remote applications 18. For example, application services 148 maybe configured to receive communications from mobile devices and/or BASdevices. Client services 146 may provide client devices with a graphicaluser interface that consumes data points and/or display data defined byequipment definitions 140 and mapped by equipment objects 144. Varioususer interfaces provided by client services 146 are described in greaterdetail with reference to FIGS. 5-35.

Still referring to FIG. 3, memory 138 is shown to include a buildingobject creation module 152. Building object creation module 152 may beconfigured to create the building objects stored in building objects142. Building object creation module 152 may create a software buildingobject for various spaces within building 10. Building object creationmodule 152 can create a building object for a space of any size orgranularity. For example, building object creation module 152 can createa building object representing an entire building, a floor of abuilding, or individual rooms on each floor. In some embodiments,building object creation module 152 creates and/or stores a buildingobject in memory 138 for each zone or room of building 10.

The building objects created by building object creation module 152 canbe accessed by UI clients 16 and remote applications 18 to provide acomprehensive user interface for controlling and/or viewing informationfor a particular building zone. Building objects 142 can group otherwiseungrouped or unassociated devices so that the group may be addressed orhandled by applications together and in a consistent manner (e.g., asingle user interface for controlling all of the BAS devices that affecta particular building zone or room). In some embodiments, buildingobject creation module 152 uses the systems and methods described inU.S. patent application Ser. No. 12/887,390, filed Sep. 21, 2010, forcreating software defined building objects.

In some embodiments, building object creation module 152 provides a userinterface for guiding a user through a process of creating buildingobjects. For example, building object creation module 152 may provide auser interface to client devices (e.g., via client services 146) thatallows a new space to be defined. In some embodiments, building objectcreation module 152 defines spaces hierarchically. For example, the userinterface for creating building objects may prompt a user to create aspace for a building, for floors within the building, and/or for roomsor zones within each floor.

In some embodiments, building object creation module 152 createsbuilding objects automatically or semi-automatically. For example,building object creation module 152 may automatically define and createbuilding objects using data imported from another data source (e.g.,user view folders, a table, a spreadsheet, etc.). In some embodiments,building object creation module 152 references an existing hierarchy forBAS 11 to define the spaces within building 10. For example, BAS 11 mayprovide a listing of controllers for building 10 (e.g., as part of anetwork of data points) that have the physical location (e.g., roomname) of the controller in the name of the controller itself. Buildingobject creation module 152 may extract room names from the names of BAScontrollers defined in the network of data points and create buildingobjects for each extracted room. Building objects may be stored inbuilding objects 142.

Still referring to FIG. 3, memory 138 is shown to include an equipmentdefinition module 154. Equipment definition module 154 may be configuredto create equipment definitions for various types of building equipmentand to store the equipment definitions in equipment definitions 140. Insome embodiments, equipment definition module 154 creates equipmentdefinitions by abstracting the data points provided by archetypalcontrollers (e.g., typical or representative controllers) for varioustypes of building equipment. For example, equipment definition module154 may receive a user selection of an archetypal controller via a userinterface. The archetypal controller may be specified as a user input orselected automatically by equipment definition module 154. In someembodiments, equipment definition module 154 selects an archetypalcontroller for building equipment associated with a terminal unit suchas a VMA.

Equipment definition module 154 may identify one or more data pointsassociated with the archetypal controller. Identifying one or more datapoints associated with the archetypal controller may include accessing anetwork of data points provided by BAS 11. The network of data pointsmay be a hierarchical representation of data points that are measured,calculated, or otherwise obtained by various BAS devices. BAS devicesmay be represented in the network of data points as nodes of thehierarchical representation with associated data points depending fromeach BAS device. Equipment definition module 154 may find the nodecorresponding to the archetypal controller in the network of data pointsand identify one or more data points which depend from the archetypalcontroller node.

Equipment definition module 154 may generate a point definition for eachidentified data point of the archetypal controller. Each pointdefinition may include an abstraction of the corresponding data pointthat is applicable to multiple different controllers for the same typeof building equipment. For example, an archetypal controller for aparticular VMA (i.e., “VMA-20”) may be associated an equipment-specificdata point such as “VMA-20.DPR-POS” (i.e., the damper position ofVMA-20) and/or “VMA-20.SUP-FLOW” (i.e., the supply air flow rate throughVMA-20). Equipment definition module 154 abstract the equipment-specificdata points to generate abstracted data point types that are generallyapplicable to other equipment of the same type. For example, equipmentdefinition module 154 may abstract the equipment-specific data point“VMA-20.DPR-POS” to generate the abstracted data point type “DPR-POS”and may abstract the equipment-specific data point “VMA-20.SUP-FLOW” togenerate the abstracted data point type “SUP-FLOW.” Advantageously, theabstracted data point types generated by equipment definition module 154can be applied to multiple different variants of the same type ofbuilding equipment (e.g., VMAs from different manufacturers, VMAs havingdifferent models or output data formats, etc.).

In some embodiments, equipment definition module 154 generates auser-friendly label for each point definition. The user-friendly labelmay be a plain text description of the variable defined by the pointdefinition. For example, equipment definition module 154 may generatethe label “Supply Air Flow” for the point definition corresponding tothe abstracted data point type “SUP-FLOW” to indicate that the datapoint represents a supply air flow rate through the VMA. The labelsgenerated by equipment definition module 154 may be displayed inconjunction with data values from BAS devices as part of a user-friendlyinterface.

In some embodiments, equipment definition module 154 generates searchcriteria for each point definition. The search criteria may include oneor more parameters for identifying another data point (e.g., a datapoint associated with another controller of BAS 11 for the same type ofbuilding equipment) that represents the same variable as the pointdefinition. Search criteria may include, for example, an instance numberof the data point, a network address of the data point, and/or a networkpoint type of the data point.

In some embodiments, search criteria includes a text string abstractedfrom a data point associated with the archetypal controller. Forexample, equipment definition module 154 may generate the abstractedtext string “SUP-FLOW” from the equipment-specific data point“VMA-20.SUP-FLOW.” Advantageously, the abstracted text string matchesother equipment-specific data points corresponding to the supply airflow rates of other BAS devices (e.g., “VMA-18.SUP-FLOW,”“SUP-FLOW.VMA-01,” etc.). Equipment definition module 154 may store aname, label, and/or search criteria for each point definition in memory138.

Equipment definition module 154 may use the generated point definitionsto create an equipment definition for a particular type of buildingequipment (e.g., the same type of building equipment associated with thearchetypal controller). The equipment definition may include one or moreof the generated point definitions. Each point definition defines apotential attribute of BAS devices of the particular type and providessearch criteria for identifying the attribute among other data pointsprovided by such BAS devices.

In some embodiments, the equipment definition created by equipmentdefinition module 154 includes an indication of display data for BASdevices that reference the equipment definition. Display data may defineone or more data points of the BAS device that will be displayed via auser interface. In some embodiments, display data are user defined. Forexample, equipment definition module 154 may prompt a user to select oneor more of the point definitions included in the equipment definition tobe represented in the display data. Display data may include theuser-friendly label (e.g., “Damper Position”) and/or short name (e.g.,“DPR-POS”) associated with the selected point definitions.

In some embodiments, equipment definition module 154 provides avisualization of the equipment definition via a graphical userinterface. The visualization of the equipment definition may include apoint definition portion which displays the generated point definitions,a user input portion configured to receive a user selection of one ormore of the point definitions displayed in the point definition portion,and/or a display data portion which includes an indication of anabstracted data point corresponding to each of the point definitionsselected via the user input portion. The visualization of the equipmentdefinition can be used to add, remove, or change point definitionsand/or display data associated with the equipment definitions. Anexample of a graphical user interface for visualizing equipmentdefinitions is described in greater detail with reference to FIG. 12.

Equipment definition module 154 may generate an equipment definition foreach different type of building equipment in BAS 11 (e.g., VMAs,chillers, AHUs, etc.). Equipment definition module 154 may store theequipment definitions in a data storage device (e.g., memory 138,equipment definitions 140, an external or remote data storage device,etc.).

Still referring to FIG. 3, memory 138 is shown to include an equipmentobject creation module 156. Equipment object creation module 156 may beconfigured to create equipment objects for various BAS devices. In someembodiments, equipment object creation module 156 creates an equipmentobject by applying an equipment definition to the data points providedby a BAS device. For example, equipment object creation module 156 mayreceive an equipment definition created by equipment definition module154. Receiving an equipment definition may include loading or retrievingthe equipment definition from a data storage device.

In some embodiments, equipment object creation module 156 determineswhich of a plurality of equipment definitions to retrieve based on thetype of BAS device used to create the equipment object. For example, ifthe BAS device is a VMA, equipment object creation module 156 mayretrieve the equipment definition for VMAs; whereas if the BAS device isa chiller, equipment object creation module 156 may retrieve theequipment definition for chillers. The type of BAS device to which anequipment definition applies may be stored as an attribute of theequipment definition. Equipment object creation module 156 may identifythe type of BAS device being used to create the equipment object andretrieve the corresponding equipment definition from the data storagedevice.

In other embodiments, equipment object creation module 156 receives anequipment definition prior to selecting a BAS device. Equipment objectcreation module 156 may identify a BAS device of BAS 11 to which theequipment definition applies. For example, equipment object creationmodule 156 may identify a BAS device that is of the same type ofbuilding equipment as the archetypal BAS device used to generate theequipment definition. In various embodiments, the BAS device used togenerate the equipment object may be selected automatically (e.g., byequipment object creation module 156), manually (e.g., by a user) orsemi-automatically (e.g., by a user in response to an automated promptfrom equipment object creation module 156). An example user interfacefor creating building objects is described in greater detail withreference to FIGS. 15-18.

In some embodiments, equipment object creation module 156 creates anequipment discovery table based on the equipment definition. Forexample, equipment object creation module 156 may create an equipmentdiscovery table having attributes (e.g., columns) corresponding to thevariables defined by the equipment definition (e.g., a damper positionattribute, a supply air flow rate attribute, etc.). Each column of theequipment discovery table may correspond to a point definition of theequipment definition. The equipment discovery table may have columnsthat are categorically defined (e.g., representing defined variables)but not yet mapped to any particular data points. An example of such anequipment discovery table is described in greater detail with referenceto FIG. 16.

Equipment object creation module 156 may use the equipment definition toautomatically identify one or more data points of the selected BASdevice to map to the columns of the equipment discovery table. Equipmentobject creation module 156 may search for data points of the BAS devicethat satisfy one or more of the point definitions included in theequipment definition. In some embodiments, equipment object creationmodule 156 extracts a search criterion from each point definition of theequipment definition. Equipment object creation module 156 may access adata point network of the building automation system to identify one ormore data points associated with the selected BAS device. Equipmentobject creation module 156 may use the extracted search criterion todetermine which of the identified data points satisfy one or more of thepoint definitions.

In some embodiments, equipment object creation module 156 automaticallymaps (e.g., links, associates, relates, etc.) the identified data pointsof selected BAS device to the equipment discovery table. A data point ofthe selected BAS device may be mapped to a column of the equipmentdiscovery table in response to a determination by equipment objectcreation module 156 that the data point satisfies the point definition(e.g., the search criteria) used to generate the column. For example, ifa data point of the selected BAS device has the name “VMA-18.SUP-FLOW”and a search criterion is the text string “SUP-FLOW,” equipment objectcreation module 156 may determine that the search criterion is met.Accordingly, equipment object creation module 156 may map the data pointof the selected BAS device to the corresponding column of the equipmentdiscovery table.

Advantageously, equipment object creation module 156 may create multipleequipment objects and map data points to attributes of the createdequipment objects in an automated fashion (e.g., without humanintervention, with minimal human intervention, etc.). The searchcriteria provided by the equipment definition facilitates the automaticdiscovery and identification of data points for a plurality of equipmentobject attributes. Equipment object creation module 156 may label eachattribute of the created equipment objects with a device-independentlabel derived from the equipment definition used to create the equipmentobject. The equipment objects created by equipment object creationmodule 156 can be viewed (e.g., via a user interface) and/or interpretedby data consumers in a consistent and intuitive manner regardless ofdevice-specific differences between BAS devices of the same generaltype. The equipment objects created by equipment object creation module156 may be stored in equipment objects 144.

Still referring to FIG. 3, memory 138 is shown to include an objectrelationship module 158. Object relationship module 158 may beconfigured to establish relationships between equipment objects 144. Insome embodiments, object relationship module 158 establishes causalrelationships between equipment objects 144 based on the ability of oneBAS device to affect another BAS device. For example, objectrelationship module 158 may establish a causal relationship between aterminal unit (e.g., a VMA) and an upstream unit (e.g., an AHU, achiller, etc.) which affects an input provided to the terminal unit(e.g., air flow rate, air temperature, etc.).

Object relationship module 158 may establish relationships betweenequipment objects 144 and building objects 142 (e.g., spaces). Forexample, object relationship module 158 may associate equipment objects144 with building objects 142 representing particular rooms or zones toindicate that the equipment object serves that room or zone. In someembodiments, object relationship module 158 provides a user interfacethrough which a user can define relationships between equipment objects144 and building objects 142. For example, a user can assignrelationships in a “drag and drop” fashion by dragging and dropping abuilding object and/or an equipment object into a “serving” cell of anequipment object provided via the user interface to indicate that theBAS device represented by the equipment object serves a particular spaceor BAS device. An example of a user interface for establishingrelationships between objects is described in greater detail withreference to FIGS. 25-26.

Still referring to FIG. 3, memory 138 is shown to include a buildingcontrol services module 160. Building control services module 160 may beconfigured to automatically control BAS 11 and the various subsystemsthereof. Building control services module 160 may utilize closed loopcontrol, feedback control, PI control, model predictive control, or anyother type of automated building control methodology to control theenvironment (e.g., a variable state or condition) within building 10.

Building control services module 160 may receive inputs from sensorydevices (e.g., temperature sensors, pressure sensors, flow rate sensors,humidity sensors, electric current sensors, cameras, radio frequencysensors, microphones, etc.), user input devices (e.g., computerterminals, client devices, user devices, etc.) or other data inputdevices via BAS interface 132. Building control services module 160 mayapply the various inputs to a building energy use model and/or a controlalgorithm to determine an output for one or more building controldevices (e.g., dampers, air handling units, chillers, boilers, fans,pumps, etc.) in order to affect a variable state or condition withinbuilding 10 (e.g., zone temperature, humidity, air flow rate, etc.).

In some embodiments, building control services module 160 is configuredto control the environment of building 10 on a zone-individualizedlevel. For example, building control services module 160 may control theenvironment of two or more different building zones using differentsetpoints, different constraints, different control methodology, and/ordifferent control parameters. Building control services module 160 mayoperate BAS 11 to maintain building conditions (e.g., temperature,humidity, air quality, etc.) within a setpoint range, to optimize energyperformance (e.g., to minimize energy consumption, to minimize energycost, etc.), and/or to satisfy any constraint or combination ofconstraints as may be desirable for various implementations.

In some embodiments, building control services module 160 uses thelocation of various BAS devices to translate an input received from abuilding system into an output or control signal for the buildingsystem. Building control services module 160 may receive locationinformation for BAS devices from location determination module 152. Insome embodiments, building control services module 160 automaticallysets or recommends control parameters for the BAS devices based on thelocations of the BAS devices. For example, building control servicesmodule 160 may automatically set a flow rate setpoint for a VAV boxbased on the size of the building zone in which the VAV box is located.

Building control services module 160 may determine which of a pluralityof sensors to use in conjunction with a feedback control loop based onthe locations of the sensors within building 10. For example, buildingcontrol services module 160 may use a signal from a temperature sensorlocated in a building zone as a feedback signal for controlling thetemperature of the building zone in which the temperature sensor islocated.

In some embodiments, building control services module 160 automaticallygenerates control algorithms for a controller or a building zone basedon the location of the zone in the building 10. For example, buildingcontrol services module 160 may be configured to predict a change indemand resulting from sunlight entering through windows based on theorientation of the building and the locations of the building zones(e.g., east-facing, west-facing, perimeter zones, interior zones, etc.).

Building control services module 160 may use zone location informationand interactions between adjacent building zones (rather thanconsidering each zone as an isolated system) to more efficiently controlthe temperature and/or airflow within building 10. For control loopsthat are conducted at a larger scale (i.e., floor level) buildingcontrol services module 160 may use the location of each building zoneand/or BAS device to coordinate control functionality between buildingzones. For example, building control services module 160 may considerheat exchange and/or air exchange between adjacent building zones as afactor in determining an output control signal for the building zones.

In some embodiments, building control services module 160 is configuredto optimize the energy efficiency of building 10 using the locations ofvarious BAS devices and the control parameters associated therewith.Building control services module 160 may be configured to achievecontrol setpoints using building equipment with a relatively lowerenergy cost (e.g., by causing airflow between connected building zones)in order to reduce the loading on building equipment with a relativelyhigher energy cost (e.g., chillers and roof top units). For example,building control services module 160 may be configured to move warmerair from higher elevation zones to lower elevation zones by establishingpressure gradients between connected building zones.

Referring now to FIG. 4, a block diagram illustrating logicalrelationships between various components of BAS 11 is shown, accordingto an exemplary embodiment. BAS 11 is shown to include a BAS controller12 and BAS equipment 52. BAS controller 12 may be the same as previouslydescribed with reference to FIGS. 2-3. BAS equipment 52 may include anynumber or type of BAS devices within or around building 10. For example,BAS equipment 52 may include BAS subsystems, controllers, chillers,rooftop units, fire and security systems, elevator systems, thermostats,lighting, serviceable equipment (e.g., vending machines), terminalunits, intermediate systems, central plants, and/or any other type ofequipment or system that can be used to control, automate, or otherwisecontribute to an environment, state, or condition of building 10.

BAS controller 12 and BAS equipment 52 both interact with data pointsnetwork 50. Data points network 50 may include a collection of datapoints that are produced (e.g., measured, calculated, etc.) by BASequipment 52. Data points network 50 may include any number of datapoints (0 . . . n). Data values output by BAS equipment 52 may be mappedto various data points of data points network 50. Each BAS device maymap data values to any number of data points (0 . . . n). BAS controller12 may read data points from data points network 50 and/or write datapoints to data points network 50. For example, BAS controller 12 mayread measured values produced by BAS equipment 52 and write setpointvalues and/or control signal values.

In various embodiments, data points network 50 organizes data pointshierarchically (e.g., in a network tree), by network location, oraccording to any other logical structure. Data points network 50 maydistinguish data points by a reference name, a location (e.g., a networkpath), and/or a particular BAS device with which the data points areassociated. BAS controller 12 may access data points network 50 toidentify BAS equipment 52 and to identify data points associated withparticular BAS devices. For example, BAS controller 12 may access datapoints network 50 to identify data points that are associated with aparticular controller.

Still referring to FIG. 4, BAS equipment 52 is shown serving spaces 56.Spaces 56 may be rooms, floors, zones, buildings, or other physicalspaces. Any quantity of BAS equipment 52 (0 . . . n) may serve anynumber of spaces 56. For example, a single upstream unit (e.g., achiller, an AHU, etc.) may serve multiple different spaces 56, whereas aterminal unit (e.g., a VMA, a VAV box, etc.) may serve a single space56. BAS equipment 52 can also serve other BAS equipment 52. For example,a chiller can serve an AHU, which can serve one or more VAV boxes.

Relationships between BAS equipment 52 and the spaces served by such BASequipment may be indicated by the names and/or network locations of thedata points associated with BAS equipment 52. For example, a data valueoutput by a BAS device may be mapped to a data point with the name ornetwork address including the text string “Building1.Floor4.Room4”indicating that that the data point is produced by a device serving Room4 on Floor 4 of Building 1. In some embodiments, BAS controller 12accesses data points network 50 to automatically determine relationshipsbetween building equipment 52 and spaces 56. Relationships betweenbuilding equipment 52 and other building equipment 52 and/or spaces 56can be established automatically or in a drag-and-drop fashion, asdescribed in greater detail with reference to FIGS. 25-26.

Still referring to FIG. 4, BAS controller 12 is shown reading andwriting equipment definitions 54. As described with reference to FIG. 3,BAS controller may create equipment definitions 54 based on the datapoints associated with archetypal controllers (e.g., as indicated bydata points network 50) for BAS equipment 52 of various types. BAScontroller 12 may use equipment definitions 54 to automatically createequipment objects. BAS controller 12 may apply equipment definitions 54to a set of data points associated with various controllers (e.g., asindicated by data points network 50) to automatically map data pointsfrom data points network 50 to attributes of the created equipmentobjects.

BAS equipment 52 is shown referencing an equipment definition 54. Eachequipment definition 54 may apply to any number of BAS equipment 52 (0 .. . n) of the same general type. For example, the same equipmentdefinition may apply to multiple different VMAs. Each equipmentdefinition 54 may contain any number (0 . . . n) of point definitions58. Point definitions 58 may define a long name (e.g., a user-friendlydescriptive name), a short name (e.g., a shortened version of the longname), and/or a category for a particular type of data point. BAScontroller 12 may use point definitions 58 to define the columns of theequipment discovery table.

Each point definition 58 may include search criteria for identifyingdata points of a particular type. Search criteria 60 may include, forexample, an MSTP instance number, an N2 point type, an N2 point address,and/or a text string. BAS controller 12 may use search criteria 60 toidentify data points (e.g., from data points network 50) to which apoint definition applies. BAS controller may map a data point to acolumn of the equipment discovery table in response to a determinationthat the data point satisfies the search criteria 60 contained by thepoint definition 58 which defines the column.

Referring now to FIGS. 5-8, a user interface 500 for creating buildingobjects is shown, according to an exemplary embodiment. User interface500 may facilitate the creation hierarchical building objects (i.e.,software objects representing spaces within a building or complex) andmay be referred to as a spaces tree editor. As shown in FIG. 5, buildingobjects can be created by selecting “new space” icon 502 via userinterface 500. Spaces within other spaces may be represented byhierarchical building objects in user interface 500. For example, userinterface 500 is shown to include a spaces tree 504 which includes a“complex” level 516, a “building” level 518 below complex level 516, anda “floor” level 520 below building level 518. In some embodiments,spaces tree 504 includes a “room” or “zone” level below floor level 520.A user can interact with user interface 500 to create new buildingobjects at any hierarchical level.

As shown in FIG. 6, user interface 500 may include interface options fordefining spaces (e.g., newly-created spaces, existing spaces, etc.). Forexample, spaces can be assigned a name attribute 506 (e.g., “Complex”),a description attribute 508, a system category attribute 510, and/or atype attribute 512 (e.g., complex, building, floor, room, etc.). A usercan enter data into value fields 516 to define values for attributes506-512. Spaces can be associated with BAS equipment serving the spaceby selecting BAS equipment via “equipment serving” field 514.

Building objects can be defined in an automated or semi-automatedfashion by importing spaces data. As shown in FIG. 7, spaces data can bedragged and dropped into spaces tree 504 to automatically create roombuilding objects within each floor building object. As shown in FIG. 8,spaces data can be imported from a table to automatically definebuilding objects. The building objects created via user interface 500may be stored in building objects 142.

Referring now to FIGS. 9-12, a user interface 900 for creating equipmentdefinitions is shown, according to an exemplary embodiment. Referringspecifically to FIG. 9, a new equipment definition can be created forbuilding equipment of a particular type. The type of building equipmentto which the equipment definition applies can be defined via userinterface 900. For example, the equipment definition can be assigned aname attribute 902 (e.g., “Building X VAV Boxes”) and/or descriptionattribute 904 describing the type of building equipment defined by theequipment definition.

Advantageously, the building equipment to which the equipment definitionapplies can be classified by selecting a system category 906 (e.g.,HVAC, lighting, security, water, etc.) via dropdown box 908. Systemcategory 906 can be used as an attribute for filtering equipment objectsand the data points associated therewith. In some embodiments, equipmentdefinitions can be further classified by subtype 910 (e.g., terminalunits, air handlers, central plants) via dropdown box 912 and/or by IDset 914 (e.g., critical, diagnostic, operational, etc.) via dropdown box916. Filtering by system and data category may be useful in managingdata from multiple building systems.

Referring specifically to FIG. 10, creating the equipment definition mayinclude identifying an archetypal BAS device for the type of buildingequipment to which the equipment definition will apply. An archetypalBAS device may be a typical or representative BAS device defined by theequipment definition. In some embodiments, identifying an archetypal BASdevice includes selecting an archetypal BAS device via data pointsnetwork 1000. Data points network 1000 may be the same or similar todata points network 50, described with reference to FIG. 4. For example,data points network 1000 is shown to include a VMA controller 1002(i.e., “VMA-20”) and a plurality of data points 1004 associated with VMAcontroller 1002. Although only one BAS device is shown in FIG. 10, it isunderstood that data points network 1000 may include any number of BASdevices.

Referring specifically to FIG. 11, an interface 1100 for visualizingdata points network 1000 is shown, according to an exemplary embodiment.Each data point in data points network 1000 may include one or moreattributes 1102 and associated values 1104. Both of the data pointsshown in FIG. 11 are N2 data points and are shown to include theattributes “net point type” 1108 and “net point address” 1110. Otherdata point attributes 1102 may include, for example, a data point name1106 (e.g., “VMA-20.OCC-C,” “4800.4818-T,” etc.), an instance value(e.g., if the data point is an MSTP data point), and/or any otherattributes of a data point that may be useful for classifying ordescribing the source or type of data associated with data points 1004.

It should be noted that data point attributes 1102 may include areference attribute 1112 identifying a particular BAS device and/or dataoutput of the BAS device to which the corresponding data point ismapped. Although reference attribute 1112 is not required for creatingequipment definitions, reference attribute 1112 may be useful in mappingattributes of equipment objects to the data values referenced by datapoints 1004 (described in greater detail with reference to FIGS. 19-21).

Referring specifically to FIG. 12, a user interface 1200 for creatingand visualizing an equipment definition is shown, according to anexemplary embodiment. User interface 1200 is shown to include a pointdefinition portion 1202 and a display data portion 1204. Pointdefinition portion 1202 is shown to include a plurality of pointdefinitions 1206. Each point definition 1206 is represented by a row inpoint definition portion 1202. Point definitions 1206 may be the same orsimilar to point definitions 58, described with reference to FIG. 4. Forexample, each point definition 1206 is shown to include a label 1208(e.g., a description of the type of data point defined by the pointdefinition), a short name 1210 (e.g., an abbreviation for label 208), acategory 1212 (e.g., generic), a source attribute 1214 (e.g., presentvalue), and search criteria 1224. Search criteria 1224 may include oneor more attributes that define data points to which the point definitionapplies. For example, search criteria 1224 are shown to include aninstance attribute 1216, a net point address attribute 1218, a net pointtype attribute 1220, and a text string 1222.

Advantageously, point definitions 1206 may be generated automatically(e.g., by equipment definition module 154) from data points 1004associated with the archetypal BAS device. For example, data points 1004can be dragged and dropped into point definition portion 1202. In otherembodiments, equipment definition module 154 automatically identifiesdata points 1004 and imports data points 1004 without requiring useraction or intervention. Attributes of data points 1004 (defined by datapoints network 1000) are used to populate values for attributes1208-1222 of point definitions 1206. For example, the value of net pointtype attribute 1108 (e.g., ADI, AI, etc.) obtained from data pointsnetwork 1000 may be used as the value for net point type attribute 1220.The value of net point address attribute 1110 obtained from data pointsnetwork 1000 (e.g., 165, 4, etc.) may be used as the value for net pointaddress attribute 1218.

In some embodiments, name attribute 1106 abstracted to generate shortname attribute 1210 and/or text string 1222. For example, the nameattribute 1106 “VMA-20.OCC-C” may be abstracted to generate the shortname attribute 1210 “OCC-C” and text string 1222 “*OCC-C*” where the “*”characters are wildcards. Advantageously, abstracted attributes 1210 and1222 may be applicable to multiple different variants of the same typeof building equipment (e.g., VMAs from different manufacturers, VMAshaving different models or output data formats, etc.), therebyfacilitating broad application of the equipment definition.

Label attribute 1208 may be a user-friendly label for each pointdefinition 1206. The user-friendly label may be a plain text descriptionof the variable defined by the point definition. For example, the label“Supply Air Flow” indicates that the data point corresponding to thepoint definition represents a supply air flow rate through the VMA. Thevalues of label attribute 1208 may be displayed in conjunction with datavalues from BAS devices as part of a user-friendly interface.

Still referring to FIG. 12, point definition portion 1202 is shown toinclude a display data input 1226. Display data input 1226 is configuredto receive a user selection of one or more point definitions 1206 asdisplay data. For example, a user may check a checkbox in the row for apoint definition to indicate a user selection of the point definition asdisplay data. Display data portion 1204 is shown to include anindication of the point definitions that have been marked as displaydata in point definition portion 1202. In some embodiments, display dataportion 1204 includes the label 1208 and short name 1210 for eachselected point definition. Display data portion 1204 may define one ormore data points that will be displayed via a user interface.

In some embodiments, the display priority of display data 1204 can beadjusted via order adjustment inputs 1228. For example, a user canselect order adjustment inputs 1228 to move an item of display data 1204up or down in the list. The display priority of display data 1204determines which data points represented by display data 1204 will bedisplayed when not all of the selected data points can be shown (e.g.,for user interfaces that display only a few items of display data 1204).

Referring now to FIGS. 13-14, two block diagrams 1300 and 1400illustrating the applicability of equipment definitions to a variety ofdifferent BAS equipment are shown, according to an exemplary embodiment.Referring specifically to FIG. 13, an equipment definition 1302 for afan coil unit (FCU) can be referenced by multiple different FCUs. Forexample, equipment definition 1302 can be referenced by a first FCU 1304(i.e., “FCU-1”) manufactured by a first manufacturer (i.e.,“manufacturer X”), a second FCU 1306 (i.e., “FCU-2”) manufactured by asecond manufacturer (i.e., “manufacturer Y”), and a nth FCU 1308 (i.e.,“FCU-n”) manufactured by a nth manufacturer (i.e., “manufacturer Z”).FCUs 1304-1308 may vary with respect to equipment vendor, model, versionmanufacturer, and/or other factors. Advantageously, each of FCUs1304-1308 can reference the same equipment definition 1302, regardlessof equipment-specific variations, due to the abstraction of data pointsused to generate equipment definition 1302.

Referring specifically to FIG. 14, an equipment definition 1402 for alighting fixture can be referenced by multiple different lightingfixtures. For example, equipment definition 1402 can be referenced by afirst lighting fixture 1404 (i.e., “Fixture-1”) manufactured by a firstmanufacturer (i.e., “manufacturer X”), a second lighting fixture 1406(i.e., “Fixture-2”) manufactured by a second manufacturer (i.e.,“manufacturer Y”), and a nth lighting fixture 1408 (i.e., “Fixture-n”)manufactured by a nth manufacturer (i.e., “manufacturer Z”). Lightingfixtures 1404-1408 may vary with respect to equipment vendor, model,version manufacturer, and/or other factors. Advantageously, each oflighting fixtures 1404-1408 can reference the same equipment definition1402, regardless of equipment-specific variations, due to theabstraction of data points used to generate equipment definition 1402.Equipment definitions can be created for any type of BAS equipment onany level within BAS 11.

Referring now to FIGS. 15-18, a user interface 1500 for creatingequipment objects is shown, according to an exemplary embodiment. Userinterface 1500 may be generated by equipment object creation module 156to guide a user through the process of creating equipment objects (forembodiments in which equipment object creation is not fully automated).Referring specifically to FIG. 15, a list of equipment definitions 1502is shown. User interface 1500 may access the data storage device inwhich equipment definitions 1502 are stored (e.g., memory 138, equipmentdefinitions 140, etc.) and provide a visualization of availableequipment definitions 1502. A user can select one or more of equipmentdefinitions 1502 via user interface 1500.

Referring specifically to FIG. 16, an equipment discovery table 1600 maybe created (e.g., by equipment object creation module 156) based on theselected equipment definition. Equipment discovery table 1600 is shownto include columns 1602, 1604, and 1616. Each of columns 1602-1606 maybe defined by the point definitions of the selected equipmentdefinition. For example, if the selected equipment definition includespoint definitions for the data points “Occupied Command,” “RoomTemperature,” and “Damper Position,” equipment discovery table 1600 mayinclude columns for each of the defined data points. In someembodiments, each of columns 1602-1606 includes the label (e.g., label1208) and short name (e.g., short name 1210) for the corresponding pointdefinition. In some embodiments, equipment discovery table 1600 includesan indication 1608 of the equipment definition used to generate theequipment discovery table.

As shown in FIG. 16, equipment discovery table 1600 has not been mappedto any particular data points. Thus, the values for columns 1602-1606 inFIG. 16 are not yet defined. Although only three columns are shown inFIG. 16, it is understood that equipment discovery table 1600 can haveany number of columns. For example, if the selected equipment definitionhas a greater number of point definitions, equipment discovery table1600 may have a greater number of columns.

Referring specifically to FIGS. 17-18, equipment discovery table 1600 isshown to include a plurality of columns 1602-1616. In addition tocolumns 1602-1606 (described with reference to FIG. 16), equipmentdiscovery table 1600 is shown to include a “Box Heating Valve Command”column 1608, a “Radiant Heating Valve Command” column 1610, a “SupplyAir Flow” column 1612, a “Supply Air Flow Setpoint” column 1614, and a“Room Temperature Setpoint” column 1616. Each of columns 1602-1616 maycorrespond to a point definition of the selected equipment definition.

Advantageously, the data point mappings for columns 1602-1616 can beautomatically populated for various BAS devices. For example, a user candrag and drop BAS devices 1702 from BAS network tree 1700 into equipmentdiscovery table 1600. Each of BAS devices 1702 is shown as a separaterow in FIG. 18. Columns 1602-1616 may be automatically mapped to aparticular data point for each of BAS devices 1702 based on theequipment definition used to generate equipment discovery table 1600.The automated mapping of data points to columns of the equipmentdiscovery table is described in greater detail with reference to FIGS.19-22.

Referring now to FIGS. 19-21, an illustration of a process forautomatically mapping data points to columns of an equipment discoverytable is shown, according to an exemplary embodiment. The illustratedprocess may be performed in response to a user dragging and dropping BASdevices into an equipment discovery table or automatically (e.g.,without requiring user action). Referring specifically to FIG. 20,equipment object creation module 156 may access data points network 1000to identify all of the data points 1012 associated with each BAS devicefor which an equipment object will be generated. For example, togenerate an equipment object for the BAS device “VMA-33,” all of thedata points 1012 associated with VMA-33 may be identified. If multipleequipment objects will be generated (e.g., if a user drags multiple BASdevices into the equipment discovery table), equipment object creationmodule 156 data points may identify a list of data points associatedwith each BAS device for which an equipment object will be generated.

Referring specifically to FIG. 19, an equipment definition 1900 havingthree point definitions 1906 is shown, according to an exemplaryembodiment. Each of point definitions 1906 includes search criteria1908. For the illustration shown in FIGS. 19-21, it is assumed thatequipment definition 1900 was used to generate the equipment discoverytable. Equipment object creation module 156 accesses equipmentdefinition 1900 to identify the search criteria 1908 for each of pointdefinitions 1906.

Equipment object creation module 156 uses search criteria 1908 toidentify data points for BAS devices that satisfy point definitions1906. For example, equipment object creation module 156 may search theattributes of data points 1012 for values that match one or more ofsearch criteria 1908. In some embodiments, equipment object creationmodule 156 performs an iterative process for each BAS device and eachpoint definition (described in greater detail with reference to FIG.22). For example, equipment object creation module 156 may use thesearch criteria 1908 corresponding to a first point definition 1906(e.g., “zone temperature”) to determine whether any of data points 1012satisfy the first point definition. As shown in FIG. 20, data point 1008satisfies the search criteria “*-T*” for the zone temperature pointdefinition 1910. In response to a determination that a data pointsatisfies the search criteria for a point definition, equipment objectcreation module 156 may automatically map the data point to a column ofthe equipment discovery table associated with the point definition.

Referring particularly to FIG. 21, an equipment object 2100 is shown,according to an exemplary embodiment. Equipment object 2100 hasattributes that correspond to point definitions 1906. For example,equipment object 2100 is shown to include a zone temperature attribute2102 corresponding to zone temperature point definition 1910, anoccupancy attribute 2104 corresponding to occupancy point definition1912, and a zone temperature setpoint attribute 2106 corresponding tozone temperature setpoint point definition 1914. Each of attributes2102-2106 is mapped to a data point identified using the search criteriaof the corresponding point definition. As shown in FIG. 21, occupancydata point 1006 is mapped to occupancy attribute 2104, zone temperaturedata point 1008 is mapped to zone temperature attribute 2102, and zonetemperature setpoint data point 1010 is mapped to zone temperaturesetpoint attribute 2106.

Referring now to FIG. 22, a flowchart of an process 2200 forautomatically mapping data points to attributes of an equipment objectis shown, according to an exemplary embodiment. Process 2200 may beperformed by equipment object creation module 156 as described withreference to FIG. 4. As shown in FIG. 22, process 2200 may be aniterative process. For example, process 2200 may begin (step 2202) withequipment object creation module 156 receiving a request to createequipment objects for multiple BAS devices (e.g., in response to a userdragging and dropping multiple BAS devices into an equipment discoverytable).

Process 2200 is shown to include iterating through a list of BAS devices(step 2204). The list of BAS devices may be a user defined list (e.g., auser selection of devices) or an automatically defined list (e.g., allBAS devices of a particular type). Each iteration of step 2204 mayinclude determining whether the last BAS device in the list has beenfully processed (step 2206). If the last BAS device has not yet beenfully processed (i.e., the result of step 2206=no), process 2200 isshown to include accessing an equipment definition for the BAS device ofthe current iteration (e.g., the equipment definition used to generatethe equipment discovery table) to identify one or more point definitions(step 2208).

Process 2200 is shown to include iterating through each point definitionidentified in step 2208 (step 2210). Each iteration of step 2210 mayinclude determining whether the last point definition in the list hasbeen fully processed (step 2212). If the last point definition has notyet been fully processed (i.e., the result of step 2212=no), process2200 is shown to include iterating through each data point associatedwith the BAS device (step 2216). The data points associated with the BASdevice may be determined by accessing the data point network. Eachiteration of step 2216 may include determining whether the last datapoint associated with the BAS device has been fully processed (step2218).

If the last data point for the BAS device has not yet been fullyprocessed (i.e., the result of step 2218=no), process 2200 is shown toinclude determining whether the data point is a MSTP data point (step2220). If the data point is a MSTP data point (i.e., the result of step2220=yes), process 2200 is shown to include determining whether theinstance number of the data point matches the instance ID of the pointdefinition (step 2222). If the instance number of the data point matchesthe instance ID of the point definition (i.e., the result of step2222=yes), process 2200 is shown to include mapping the networkreference of the data point to an equipment object attributecorresponding to the point definition (step 2230) and proceeding to thenext data point iteration (step 2216). If the instance number of thedata point does not match the instance ID of the point definition (i.e.,the result of step 2222=no), process 2200 is shown to include proceedingto the next data point iteration (step 2216) without mapping the datapoint to the attribute of the equipment object.

If the data point is not a MSTP data point (i.e., the result of step2220=no), process 2200 is shown to include determining whether the datapoint is a N2 data point (step 2224). If the data point is a N2 datapoint (i.e., the result of step 2224=yes), process 2200 is shown toinclude determining whether the point address and type of the data pointmatch the N2 address and type of the point definition (step 2226). Ifthe point address and type of the data point match the N2 address andtype of the point definition (i.e., the result of step 2226=yes),process 2200 is shown to include mapping the network reference of thedata point to an equipment object attribute corresponding to the pointdefinition (step 2230) and proceeding to the next data point iteration(step 2216). If the point address and type of the data point do notmatch the N2 address and type of the point definition (i.e., the resultof step 2226=no), process 2200 is shown to include proceeding to thenext data point iteration (step 2216) without mapping the data point tothe attribute of the equipment object.

If the point address and type of the data point does not match the N2address and type of the point definition (i.e., the result of step2224=no), process 2200 is shown to include determining whether the nameof the data point matches the search criteria text (step 2228). If thename of the data point matches the search criteria text (i.e., theresult of step 2228=yes), process 2200 is shown to include mapping thenetwork reference of the data point to an equipment object attributecorresponding to the point definition (step 2230) and proceeding to thenext data point iteration (step 2216). If the name of the data pointdoes not match the search criteria text (i.e., the result of step2228=no), process 2200 is shown to include proceeding to the next datapoint iteration (step 2216) without mapping the data point to theattribute of the equipment object.

Still referring to FIG. 22, once all of the data points have beenprocessed (i.e., the result of step 2216=yes), process 2200 is shown toinclude proceeding to the next point definition iteration (step 2210).Process 2200 may include repeating steps 2216-2230 for each pointdefinition iteration. Once all of the point definitions have beenprocessed for each data point iteration (i.e., the result of step2212=yes), process 2200 is shown to include proceeding to the next BASdevice iteration (step 2204). Process 2200 may include repeating steps2206-2230 for each BAS device iteration.

Once all of the BAS devices have been processed for each pointdefinition iteration and each data point iteration (i.e., the result ofstep 2206=yes), process 2200 is shown to include creating equipmentobjects for each BAS device using the mappings between data points andequipment object attributes established in step 2230. Process 2200 thenends and stores the equipment objects in a data storage device (step2234).

Referring now to FIG. 23, an equipment object 2300 created using process2200 is shown, according to an exemplary embodiment. Equipment object2300 has attributes 2302, 2304, and 2306 that correspond to the pointdefinitions of the equipment definition used to create equipment object2300. Advantageously, attributes 2302-2306 may be consistent acrossmultiple equipment objects generated using the same equipmentdefinition. This consistency results from the same equipment definitionbeing used to create multiple equipment objects for the same type of BASdevice.

Each of attributes 2302-2306 is mapped to a data point identified usingthe search criteria of the corresponding point definition. For example,attribute 2302 is mapped to reference 2308, attribute 2304 is mapped toreference 2310, and attribute 2306 is mapped to reference 2312. Themappings shown in FIG. 2300 are determined automatically (e.g., byequipment object creation module 156) by identifying the referencevalues for each data point mapped to an attribute of equipment object2300. Equipment object creation module 156 may access data pointsnetwork 1000 to discover mappings between data points and referencevalues.

Referring now to FIG. 24, a user interface 2400 for visualizingequipment objects is shown, according to an exemplary embodiment. Asshown, user interface 2400 consumes various attributes of equipmentobject 2300. For example, user interface 2400 is shown displaying zonetemperature attribute 2302, occupancy attribute 2304, and zonetemperature setpoint 2306. User interface 2400 displays attributes ofequipment object 2300, which are derived from the equipment definitionused to create equipment object 2300. User interface 2400 is shown toinclude the reference values mapped to each attribute of equipmentobject 2300. For example, user interface 2400 is shown displaying thevalue of reference attribute 2308 (i.e., 76.3° F.), the value ofreference attribute 2312 (i.e., 73.1° F.), and the value of referenceattribute 2310 (i.e., occupied).

Referring now to FIGS. 25-26, a user interface 2500 for establishingrelationships between building objects and equipment objects is shown,according to an exemplary embodiment. User interface 2500 may be used toassociate equipment objects 2602-2608 representing BAS devices withbuilding objects 2502-2508 representing particular rooms or zones. Therelationships established via user interface 2500 may indicate that aparticular BAS device serves a particular room or zone.

Relationships between building objects 2502-2508 and equipment objects2602-2608 can be assigned in a “drag and drop” fashion by dragging anddropping a building object 2502-2508 into a “serving” cell 2610-2616associated with one of equipment objects 2602-2608. As shown in FIG. 26,building object 2502 (i.e., “Room 1”) has been associated with equipmentobject 2602 (i.e., “VMA-11”) by dragging and dropping building object2502 into serving cell 2610. Building object 2504 (i.e., “Room 2”) hasbeen associated with equipment object 2604 (i.e., “VMA-12”) by draggingand dropping building object 2504 into serving cell 2612. Buildingobject 2506 (i.e., “Room 3”) has been associated with equipment object2606 (i.e., “VMA-13”) by dragging and dropping building object 2506 intoserving cell 2613. Building object 2508 (i.e., “Room 4”) has beenassociated with equipment object 2608 (i.e., “VMA-14”) by dragging anddropping building object 2508 into serving cell 2616.

In some embodiments, user interface 2500 may be used to establishrelationships between equipment objects. For example, instead ofdragging and dropping a building object into the serving cell associatedwith an equipment object, another equipment object can be dropped intothe serving cell. Relationships between equipment objects may indicatecausal relationships between various BAS devices. For example, a causalrelationship may be established between a terminal unit (e.g., a VMA)and an upstream unit (e.g., an AHU, a chiller, etc.) which affects aninput provided to the terminal unit (e.g., air flow rate, airtemperature, etc.). Upstream BAS devices can be associated withdownstream BAS devices, which can be associated with spaces. Such arelationship chain allows the various BAS devices serving a particularspace to be readily determined.

Advantageously, associating equipment objects with building objects andwith each other allows the attributes of equipment objects that serve aspace to be mapped to attributes of the building object representing thespace. A consistent and user-friendly interface can be provided formonitoring and controlling various spaces, regardless of variations inthe BAS devices which serve the spaces.

Referring now to FIGS. 27-32, several user interfaces 2700-3200 formonitoring and controlling BAS devices and spaces are shown, accordingto an exemplary embodiment. User interfaces 2700-3200 provide avisualization of data points mapped to equipment objects and/or buildingobjects using the systems and methods described with reference to FIGS.1-26. For example, user interfaces 2700-3200 may display data pointsthat have been mapped to one or more equipment objects that directlyserve a space (e.g., equipment objects for terminal units) or indirectlyserve a space (e.g., equipment objects for upstream units). Userinterfaces 2700-3200 illustrate a circle of comfort for maintainingcomfortable conditions within a space.

Referring specifically to FIGS. 27-28, user interfaces 2700 and 2800 areshown displaying an outdoor temperature 2702 and 2802, a supply airtemperature 2704 and 2804, an operating setpoint 2706 and 2806, and areturn air temperature 2708 and 2808. Each of data values 2702-2708 and2802-2808 may be mapped to an attribute of an equipment object whichserves the space. For example, data values 2702-2708 and 2802-2808 maybe mapped to user interfaces 2700 and 2800 from data points associatedwith a rooftop unit that serves the space. An operating status 2712 and2812 of the rooftop unit (e.g., cooling, heating) is shown in an upperportion of circles 2710 and 2810.

A more detailed status 2714 and 2814 of the current operating state isshown in a middle portion of circles 2710 and 2810. Numbered circlesindicate stages of heating or cooling that are available for the rooftopunit. Circles that are filled in (e.g., darkened, colored, etc.)indicate that the corresponding stage is currently powered. Occupancystatus indicators 2718 and 2818 provide an indication of the currentoccupancy status of the space (e.g., occupied, unoccupied). The lowerportion of circle 2710 displays the current space temperature. The lowerportion of circle 2810 displays thermostat control systems for thespace.

Circles 2710 and 2810 indicate a direction of airflow between locationsassociated with the displayed temperatures. For example, outdoor air iscooled or heated to provide supply air to a space. The supply air helpsthe space achieve the operating setpoint. Air from within the space isexhausted as return air back to the outdoor location.

Referring specifically to FIGS. 29-30, user interfaces 2900 and 3000 areshown displaying an outdoor temperature 2902 and 3002, a supply airtemperature 2904 and 3004, and a return air temperature 2908 and 3008.Each of data values 2902-2908 and 3002-3008 may be mapped to anattribute of an equipment object which serves the space. For example,data values 2902-2908 and 3002-3008 may be mapped to user interfaces2900 and 3000 from data points associated with a rooftop unit thatserves the space. An operating status 2912 and 3012 of the rooftop unit(e.g., air tempering, dehumidification) is shown in an upper portion ofcircles 2910 and 3010.

A more detailed status 2914 and 3014 of the current operating state isshown in a middle portion of circles 2910 and 3010. Numbered circlesindicate stages of heating or cooling that are available for the rooftopunit. Circles that are filled in (e.g., darkened, colored, etc.)indicate that the corresponding stage is currently powered. Occupancystatus indicators 2918 and 3018 provide an indication of the currentoccupancy status of the space (e.g., occupied, unoccupied). The lowerportions of circles 2910 and 3010 displays thermostat control systemsfor the space.

Referring specifically to FIGS. 31-32, user interfaces 3100 and 3200 areshown displaying an outdoor temperature 3102 and 3202, a supply airtemperature 3104 and 3204, and a return air temperature 3108 and 3208.User interface 3200 is shown to include an additional indication of anoperating setpoint 3206. Each of data values 3102-3108 and 3202-3208 maybe mapped to an attribute of an equipment object which serves the space.For example, data values 3102-3108 and 3202-3208 may be mapped to userinterfaces 3100 and 3200 from data points associated with a rooftop unitthat serves the space. An operating status 3112 and 3212 of the rooftopunit (e.g., air tempering, idle) is shown in an upper portion of circles3110 and 3210. Occupancy status indicator 3118 and 3218 provide anindication of the current occupancy status of the space (e.g., occupied,unoccupied). The lower portion of circles 3210 displays the currenttemperature of the space.

Referring now to FIGS. 33-35, user interfaces 2700-3200 can be displayedto client devices in a variety of formats. For example, FIG. 33 showsuser interface 2700 presented as part of a larger interface 3300. Userinterface 3300 displays the circle of comfort as primary content in themiddle column of interface 3300. User interface 3300 is shown to includean equipment selector 3302 (e.g., a drop down menu) configured toreceive a user selection of various BAS devices. When a different deviceis selected via equipment selector 3302, user interface 2700 may bereplaced with a user interface corresponding to the selected BAS device.

In some embodiments, user interface 3300 includes display data 3304.Display data 3304 may include one or more attributes and/or values ofthe equipment object corresponding to the selected BAS device. In someembodiments, the items displayed in display data 3304 are determined byreferencing the equipment definition used to create the equipmentobject. For example, the point definitions designated in display data inthe equipment definition may be displayed in user interface 3300. Arrowson each item of display data 3304 indicate that clicking on an item maycause a related folder within details view 3310 to be displayed.

Still referring to FIG. 33, user interface 3300 is shown to include analarms portion 3306. Alarms portion 3306 may display all active criticalalarms in a time descending order (e.g., most recent on top). Selectingthe “view all alarms” icon 3308 may cause an alarms view 3312 to bedisplayed.

Referring now to FIGS. 34 and 35, user interface 3300 is shown displayedon a mobile device. Due to the limited screen size of the mobile device,user interface 2700 and alarms portion 3306 are displayed in first view3400 and display data 3304 are displayed in a second view 3500. Views3400 and 3500 may be different views of the same page or differentpages. User interface 3300 may be displayed on a wide variety of clientdevices such as desktop computers, client terminals, laptop computers,tablets, portable communications devices, smart phones, and other typesof portable or non-portable electronic devices.

Referring now to FIG. 36, a flowchart of a process 3600 for creating anequipment definition for a type of building equipment in a buildingautomation system is shown, according to an exemplary embodiment.Process 3600 may be performed by BAS controller 12 (as described withreference to FIG. 3) to create equipment definitions for various typesof building equipment and to store the equipment definitions inequipment definitions 140. In some embodiments, equipment definitionsare created by abstracting data points provided by archetypal BASdevices (e.g., typical or representative devices) of various types ofbuilding equipment.

Process 3600 is shown to include receiving a user selection of anarchetypal device of a type of building equipment of a buildingautomation system (step 3602). In various embodiments, the archetypaldevice may be specified as a user input or selected automatically (e.g.,by equipment definition module 154). Step 3602 may include selecting orreceiving a user selection of a terminal unit such as a VMA.

Still referring to FIG. 36, process 3600 is shown to include identifyingone or more data points associated with the archetypal device (step3604). Step 3604 may include accessing a network of data points providedby BAS 11. The network of data points may be a hierarchicalrepresentation of data points that are measured, calculated, orotherwise obtained by various BAS devices. BAS devices may berepresented in the network of data points as nodes of the hierarchicalrepresentation with associated data points for each BAS device. Step3604 may include finding the node corresponding to the archetypal devicein the network of data points and identifying one or more data pointswhich associated with the archetypal device node.

Process 3600 is shown to include generating a point definition for eachidentified data point of the archetypal device (step 3606). Each pointdefinition may include an abstraction of the corresponding data pointthat is applicable to multiple different devices of the same equipmenttype. For example, an archetypal device such as a VMA (i.e., “VMA-20”)may be associated equipment-specific data points such as“VMA-20.DPR-POS” (i.e., the damper position of VMA-20) and/or“VMA-20.SUP-FLOW” (i.e., the supply air flow rate through VMA-20). Step3606 may include abstracting the equipment-specific data points togenerate abstracted data point types that are generally applicable toother equipment of the same type. For example, step 3606 may includeabstracting the equipment-specific data point “VMA-20.DPR-POS” togenerate the abstracted data point type “DPR-POS” and abstracting theequipment-specific data point “VMA-20.SUP-FLOW” to generate theabstracted data point type “SUP-FLOW.” Advantageously, the abstracteddata point types generated in step 3606 can be applied to multipledifferent variants of the same type of building equipment (e.g., VMAsfrom different manufacturers, VMAs having different models or outputdata formats, etc.).

In some embodiments, step 3606 includes generating a user-friendly labelfor each point definition. The user-friendly label may be a plain textdescription of the variable defined by the point definition. Forexample, step 3606 may include generating the label “Supply Air Flow”for the point definition corresponding to the abstracted data point type“SUP-FLOW” to indicate that the data point represents a supply air flowrate through the VMA. The labels generated in step 3606 may be displayedin conjunction with data values from BAS devices as part of auser-friendly interface.

In some embodiments, step 3606 includes generating search criteria foreach point definition. The search criteria may include one or moreparameters for identifying another data point (e.g., a data pointassociated with another controller of BAS 11 for the same type ofbuilding equipment) that represents the same variable as the pointdefinition. Search criteria may include, for example, an instance numberof the data point, a network address of the data point, and/or a networkpoint type of the data point.

In some embodiments, search criteria includes a text string abstractedfrom a data point associated with the archetypal device. For example,equipment definition module 154 may generate the abstracted text string“SUP-FLOW” from the equipment-specific data point “VMA-20.SUP-FLOW.”Advantageously, the abstracted text string matches otherequipment-specific data points corresponding to the supply air flowrates of other BAS devices (e.g., “VMA-18.SUP-FLOW,” “SUP-FLOW.VMA-01,”etc.). Step 3606 may include storing a name, label, and/or searchcriteria for each point definition in memory 138.

Still referring to FIG. 36, process 3600 is shown to include using thegenerated point definitions to create an equipment definition for thetype of building equipment (step 3608). Each equipment definition mayapply to building equipment of a particular type and may be created forthe same type of building equipment as the archetypal device. Theequipment definition may include one or more of the generated pointdefinitions. Each point definition defines a potential attribute of BASdevices of the particular type and provides search criteria foridentifying the attribute among other data points provided by such BASdevices.

In some embodiments, the equipment definition created in step 3608includes an indication of display data for BAS devices that referencethe equipment definition. Display data may define one or more datapoints of the BAS device that will be displayed via a user interface. Insome embodiments, display data are user defined. For example, step 3608may include prompting a user to select one or more of the pointdefinitions included in the equipment definition to be represented inthe display data. Display data may include the user-friendly label(e.g., “Damper Position”) and/or short name (e.g., “DPR-POS”) associatedwith the selected point definitions.

In some embodiments, step 3608 includes providing a visualization of theequipment definition via a graphical user interface. The visualizationof the equipment definition may include a point definition portion whichdisplays the generated point definitions, a user input portionconfigured to receive a user selection of one or more of the pointdefinitions displayed in the point definition portion, and/or a displaydata portion which includes an indication of an abstracted data pointcorresponding to each of the point definitions selected via the userinput portion. The visualization of the equipment definition can be usedto add, remove, or change point definitions and/or display dataassociated with the equipment definitions.

In some embodiments, step 3608 can be repeated for various differenttypes of archetypal devices to generate an equipment definition for eachdifferent type of building equipment in BAS 11 (e.g., VMAs, chillers,AHUs, etc.). Process 3600 may conclude with storing the equipmentdefinitions in a data storage device (e.g., memory 138, equipmentdefinitions 140, an external or remote data storage device, etc.) (step3610).

Referring now to FIG. 37, a flowchart of a process 3700 for using anequipment definition to create an equipment object representing buildingequipment of a building automation system is shown, according to anexemplary embodiment. Process 3700 may be performed by BAS controller 12(as described with reference to FIG. 3) to create equipment objects forvarious BAS devices and to store the equipment objects in equipmentobjects 144. In some embodiments, equipment objects are created byreferencing the equipment definitions created using process 3600.

Process 3700 is shown to include receiving an equipment definitionincluding one or more point definitions (step 3702). Each pointdefinition may include an abstraction of a data point associated with anarchetypal device of the building automation system. Point definitionsmay include, for example, a name (e.g., a user-friendly label), a shortname (e.g., an abbreviation of the user-friendly label), and/or searchcriteria for each point definition. The search criteria may include oneor more parameters for identifying a data point that corresponds to thesame variable as the point definition. Search criteria may include, forexample, an instance number of the data point, a network address of thedata point, and/or a network point type of the data point. In someembodiments, search criteria includes a text string abstracted from adata point associated with the archetypal device.

Still referring to FIG. 37, process 3700 is shown to include identifyinga second device of the building automation system of the same type asthe archetypal device (step 3704). Step 3704 may include identifying aBAS device of BAS 11 to which the equipment definition received in step3702 applies. For example, step 3704 may include identifying a BASdevice that is of the same type of building equipment as the archetypalBAS device used to generate the equipment definition.

In various embodiments, the BAS device may be identified automatically(e.g., by equipment object creation module 156), manually (e.g., by auser) or semi-automatically (e.g., by a user in response to an automatedprompt from equipment object creation module 156). In some embodiments,step 3704 includes identifying one or more BAS devices that have beenselected by a user (e.g., dragged and dropped into an equipmentdiscovery table). Step 3704 may include identifying a single BAS deviceor multiple BAS devices.

Step 3704 may be performed before or after step 3702. For embodiments inwhich step 3702 is performed first, step 3704 may include identifyingand/or selecting one or more BAS devices that are of the same type asthe BAS device used to create the equipment definition.

For embodiments in which step 3704 is performed first, step 3702 mayinclude selecting an equipment definition that applies to the BAS deviceidentified in step 3704. The type of BAS device to which an equipmentdefinition applies may be stored as an attribute of the equipmentdefinition. Step 3702 may include identifying the type of BAS deviceselected in step 3704 and retrieving the corresponding equipmentdefinition from the data storage device. For example, if the BAS deviceidentified in step 3704 is a VMA, step 3702 may include retrieving theequipment definition for VMAs. If the BAS device identified in step 3704is a chiller step 3702 may include retrieving the equipment definitionfor chillers.

Still referring to FIG. 37, process 3700 is shown to include using theequipment definition to automatically identify one or more data pointsassociated with the second device that satisfy one or more of the pointdefinitions (step 3706). Step 3706 may include accessing a network ofdata points (e.g., data points network 1000) to identify all of the datapoints associated with the second BAS device. If multiple BAS devicesare identified in step 3704 (e.g., if a user drags multiple BAS devicesinto the equipment discovery table), step 3706 may include identifying alist of data points associated with each BAS device.

Step 3706 may include accessing the equipment definition received instep 3702 to identify search criteria for each of the point definitions.In some embodiments, step 3706 includes using the search criteria todetermine which of the data points in the list of data points satisfythe point definitions. For example, step 3706 may include searchingattributes of the data points for values that match one or more ofsearch criteria. In some embodiments, step 3706 is performed as aniterative process for each BAS device and each point definition(described in greater detail with reference to FIG. 22).

Still referring to FIG. 37, process 3700 is shown to includeautomatically mapping the identified data points of the second device toan equipment object representing the second device (step 3708). Step3708 may include mapping each of the identified data points to anattribute of the equipment object. The equipment object may haveattributes that correspond to the point definitions of the equipmentdefinition received in step 3702. Each attribute of the equipment objectmay correspond to a different point definition. An example of such anequipment object is shown in FIG. 21.

Step 3708 may include mapping a data point to an attribute of theequipment object in response to a determination that the data pointsatisfies the search criteria of the point definition corresponding tothe attribute. Advantageously, step 3708 may be performed in anautomated fashion to automatically map data points to equipment objectattributes. The automated identification and mapping of data pointsfacilitates the mass creation of equipment objects for many differentBAS devices (e.g., hundreds, thousands).

Referring now to FIG. 38, a flowchart of a process 3800 for providing adisplay of data points associated with building equipment of a buildingautomation system is shown, according to an exemplary embodiment.Process 3800 may be performed by BAS controller 12 (as described withreference to FIG. 3) to provide a user interface for monitoring and/orcontrolling BAS devices and spaces in a building automation system.

Process 3800 is shown to include receiving an equipment definition for atype of building equipment (step 3802). The equipment definition mayinclude one or more point definitions. Each point definition may includean abstraction of a data point associated with an archetypal device ofthe building automation system. Point definitions may include, forexample, a name (e.g., a user-friendly label), a short name (e.g., anabbreviation of the user-friendly label), and/or search criteria foreach point definition. The search criteria may include one or moreparameters for identifying a data point that corresponds to the samevariable as the point definition. Search criteria may include, forexample, an instance number of the data point, a network address of thedata point, and/or a network point type of the data point. In someembodiments, search criteria includes a text string abstracted from adata point associated with the archetypal device.

The equipment definition may include an indication of whether each pointdefinition is identified as display data. Display data may include oneor more types of data points that will be displayed via a user interfacefor BAS devices that reference the equipment definition. In someembodiments, display data are user defined. Point definitions can beindicated as display data, for example, by selecting the pointdefinition or marking the point definition as display data (e.g.,checking a box next to the point definition). Display data may includethe user-friendly label and/or short name associated with the selectedpoint definitions.

Still referring to FIG. 38, process 3800 is shown to include using theequipment definition to automatically identify one or more data pointsthat satisfy one or more of the point definitions identified as displaydata and that are associated with a device of the same type of buildingequipment (step 3804). The BAS device may be any device to which theequipment definition applies (i.e., a device of the same type as thearchetypal BAS device used to create the equipment definition.

In some embodiments, step 3804 includes accessing a network of datapoints (e.g., data points network 1000) to identify all of the datapoints associated with a BAS device. Step 3804 may include accessing theequipment definition received in step 3802 to identify search criteriafor each of the point definitions. In some embodiments, step 3804includes using the search criteria to determine which of the data pointssatisfy the point definitions. For example, step 3804 may includesearching attributes of the data points for values that match one ormore of search criteria.

In other embodiments, step 3804 includes accessing an equipment objectassociated with the BAS device to identify one or more data pointsassociated with the device. The equipment object may define a mappingbetween attributes of the equipment object and data points. The datapoints associated with the equipment object can be assumed to satisfy atleast one of the point definitions (e.g., since satisfying a pointdefinition may be required for a data point to be mapped to an attributeof the equipment object).

Step 3804 may include determining which of the point definitions arelisted as display data in the equipment definition. Point definitionscan be listed as display data by a user (e.g., be selecting variouspoint definitions) or automatically (e.g., by smart equipment, by acontroller, etc.). In various embodiments, display data can be set bylisting one or more point definitions or otherwise indicating that datapoints qualify as display data. The equipment definition received instep 3802 can be referenced to identify one or more point definitionsthat are indicated as display data. Step 3804 may include identifyingdata points that satisfy at least one of the point definitions that areindicated as display data.

Still referring to FIG. 38, process 3800 is shown to includeautomatically mapping the identified data points to a display object(step 3806). The display object may be an equipment object (e.g., one ofequipment objects 144), a building object (e.g., one of building objects142), or another software object to which a data point can be mapped.The display object may represent a particular BAS device, a particularspace, or a combination of both. In some embodiments, the display objectincludes data points mapped from multiple different BAS devices. Forexample, the display object may represent a space within a building andmay be mapped to data points provided by multiple different devices thatserve the space (e.g., a VAV box, a lighting fixture, a window sensor,etc.).

Still referring to FIG. 38, process 3800 is shown to include generatinga user interface for display on a client device, the user interfaceincluding a display of the one or more data points mapped to the displayobject (step 3808). The user interface may be a graphical user interfacefor monitoring or controlling a BAS device and/or a space. For example,the user interface may be the same or similar to user interface 2400 orany of user interfaces 2700-3300 as described with reference to FIG. 24and FIGS. 27-35.

Referring now to FIG. 39, a “served by” interface 3900 is shown,according to an exemplary embodiment. Interface 3900 provides avisualization of the building equipment that serves a particular space(i.e., “Rm 1704” in FIG. 39) and indicates relationships between suchbuilding equipment. For example, interface 3900 indicates that the space“Rm 1704” is served by VAV box 1704, AHU-001, and a chilled watersystem. Building equipment that most directly serves a space (e.g.,equipment located in the space or which has a most direct relationshipto the space) may be displayed near the top of interface 3900, whereasbuilding equipment that more indirectly serves the space may bedisplayed further toward the bottom of interface 3900.

The arrows connecting building equipment in interface 3900 indicateserving relationships between the building equipment. For example, anarrow pointing from the chilled water system toward AHU-001 indicatesthat the chilled water system serves AHU-001. Similarly, an arrowpointing from AHU-001 to VAV box 1704 indicates that AHU-001 serves VAVbox 1704. All of the building equipment shown in interface 3900 isdisplayed under the “Rm 1704” heading, indicating that all of thedisplayed equipment serves room 1704. The attributes of each BAS deviceshown in interface 3900 may be mapped from the corresponding equipmentobject, as described with reference to FIGS. 23-24.

The equipment relationships illustrated in interface 3900 may beestablished during equipment discovery (as described with reference toFIGS. 16-18) or by dragging and dropping objects into relationship table2600 (as described with reference to FIGS. 25-26). The “serving”relationships indicated in relationship table 2600 may be used togenerate interface 3900. For example, the relationship table 2600 forthe building equipment shown in interface 3900 indicates that VAV box1704 serves Rm 1704, that AHU-001 serves VAV box 1704, and that thechilled water system serves AHU-001. These relationships are reflectedin interface 3900 as arrows between building equipment (e.g., the arrowsbetween VAV box 1704, AHU-001, and the chilled water system) and theheading of the space served by the building equipment (i.e., Rm 1704).

The construction and arrangement of the systems and methods as shown inthe various exemplary embodiments are illustrative only. Although only afew embodiments have been described in detail in this application, manymodifications are possible. For example, the position of elements may bevaried and the nature or number of discrete elements or positions may bealtered or varied. Accordingly, all such modifications are intended tobe included within the scope of the present application. The order orsequence of any process or method steps may be varied or re-sequencedaccording to alternative embodiments. Other substitutions,modifications, changes, and omissions may be made in the design,operating conditions and arrangement of the exemplary embodimentswithout departing from the scope of the present application.

The present application contemplates methods, systems and programproducts on any machine-readable media for accomplishing variousoperations. The embodiments of the present application may beimplemented using existing computer processors, or by a special purposecomputer processor for an appropriate system, incorporated for this oranother purpose, or by a hardwired system.

Embodiments within the scope of the present application include programproducts comprising machine-readable media for carrying or havingmachine-executable instructions or data structures stored thereon. Suchmachine-readable media can be any available media that can be accessedby a general purpose or special purpose computer or other machine with aprocessor. By way of example, such machine-readable media can compriseRAM, ROM, EPROM, EEPROM, CD-ROM or other optical disk storage, magneticdisk storage or other magnetic storage devices, or any other mediumwhich can be used to carry or store desired program code in the form ofmachine-executable instructions or data structures and which can beaccessed by a general purpose or special purpose computer or othermachine with a processor. Combinations of the above are also includedwithin the scope of machine-readable media. Machine-executableinstructions include, for example, instructions and data which cause ageneral purpose computer, special purpose computer, or special purposeprocessing machines to perform a certain function or group of functions.Software implementations could be accomplished with standard programmingtechniques with rule based logic and other logic to accomplish thevarious connection steps, processing steps, comparison steps anddecision steps.

Although the figures may show a specific order of method steps, theorder of the steps may differ from what is depicted. Also two or moresteps may be performed concurrently or with partial concurrence. Suchvariation will depend on the software and hardware systems chosen and ondesigner choice. All such variations are within the scope of thedisclosure. Likewise, software implementations could be accomplishedwith standard programming techniques with rule based logic and otherlogic to accomplish the various connection steps, processing steps,comparison steps and decision steps.

What is claimed is:
 1. A method of creating an equipment definition fora type of building equipment in a building automation system, the methodcomprising: identifying a first data point associated with an archetypaldevice of the type of building equipment operated to affect a variablestate or condition within a building, the first data point comprising atext string specific to the archetypal device; creating, for the firstdata point, an abstraction of the text string specific to the archetypaldevice, wherein the abstraction of the text string comprises a portionof the text string that is applicable to multiple different devices ofthe same type of building equipment; generating a point definition forthe first data point associated with the archetypal device, the pointdefinition comprising the abstraction of the text string of thecorresponding data point; using the point definition to create anequipment definition for the type of building equipment, the equipmentdefinition comprising the point definition; using the equipmentdefinition to identify a second data point associated with a seconddevice of the same type of building equipment; and automatically mappingthe second data point of the second device to an equipment objectrepresenting the second device.
 2. The method of claim 1, furthercomprising: providing a user interface to a client device, the userinterface comprising a display of one or more devices of the buildingautomation system; and receiving a user selection of the archetypaldevice via the user interface.
 3. The method of claim 1, wherein thepoint definition comprises a criterion for identifying the second datapoint associated with the second device of the same type of buildingequipment of the building automation system.
 4. The method of claim 3,wherein the criterion for identifying the second data point associatedwith the second device comprises at least one of: an instance number ofthe second data point; a network address of the second data point; and anetwork point type of the second data point.
 5. The method of claim 3,wherein the criterion for identifying the second data point associatedwith the second device comprises the abstraction of the text string ofthe corresponding data point of the archetypal device.
 6. The method ofclaim 1, further comprising providing a user interface for visualizingthe equipment definition to a client device, the user interfacecomprising: a point definition portion comprising a display of the pointdefinition; a user input portion configured to receive a user selectionof the point definition displayed in the point definition portion; and adisplay data portion comprising an indication of an abstracted datapoint corresponding to the point definition selected via the user inputportion.
 7. The method of claim 1, further comprising: receiving a userselection of the first point definition; and automatically mapping asecond data point of a second device that satisfy the selected pointdefinition to a user interface for visualizing data associated with thesecond device.
 8. The method of claim 1, further comprising: associatingthe equipment definition with a category of building equipment; andusing the equipment definition to filter building equipment of thebuilding automation system by the category associated with the equipmentdefinition.
 9. A method of using an equipment object representingbuilding equipment of a building automation system, the methodcomprising: obtaining an equipment definition for a type of buildingequipment, the equipment definition comprising one or more pointdefinitions, each point definition comprising an abstraction of a textstring extracted from a data point associated with an archetypal deviceof the type of building equipment; identifying a second device of thebuilding automation system of the same type as the archetypal device;using the equipment definition to identify one or more data pointsassociated with the second device that satisfy one or more of the pointdefinitions; mapping the identified data points of the second device toan equipment object representing the second device; using the equipmentobject to monitor or control the second device to affect a variablestate or condition within a building; using the equipment definition toautomatically identify one or more of the point definitions indicated asdisplay data; and automatically mapping a data point of the seconddevice to a display object representing the second device in response toa determination that the data point satisfies one or more of the pointdefinitions indicated as display data.
 10. The method of claim 9,wherein each point definition comprises a criterion for identifying adata point associated with the second device.
 11. The method of claim10, wherein the criterion for identifying the data point associated withthe second device comprises at least one of: an instance number of thedata point; a network address of the data point; and a network pointtype of the data point.
 12. The method of claim 10, wherein thecriterion for identifying the data point associated with the seconddevice comprises the abstraction of the text string extracted from acorresponding data point associated with the archetypal device.
 13. Themethod of claim 9, wherein using the equipment definition to identifyone or more data points associated with the second device comprises:extracting a search criterion from each point definition of theequipment definition; accessing a network of the building automationsystem to determine one or more data points associated with the seconddevice; using the extracted search criterion to search the data pointsof the second device for a data point that satisfies the searchcriterion; and identifying the data point that satisfies the searchcriterion as a data point associated with the second device thatsatisfies one or more of the point definitions.
 14. The method of claim9, wherein automatically mapping the identified data points of thesecond device to the equipment object comprises: determining a networkaddress for each identified data point of the second device; and mappingthe network address for each identified data point of the second deviceto the equipment object representing the second device.
 15. The methodof claim 14, wherein determining a network address for each identifieddata point of the second device comprises: accessing a data pointnetwork for the building automation system; and using the data pointnetwork to identify an existing relationship between the network addressand an identified data point of the second device.
 16. The method ofclaim 9, further comprising providing a user interface to a clientdevice, the user interface comprising a display of the one or more datapoints mapped to the display object.
 17. A method of providing a displayof data points associated with building equipment of a buildingautomation system, the method comprising: obtaining an equipmentdefinition for a type of building equipment, the equipment definitioncomprising a point definition and an indication of whether the pointdefinition is identified as display data, the point definitioncomprising an abstraction of a text string extracted from a data pointassociated with an archetypal device of the type of building equipment;using the equipment definition to automatically identify a data pointthat satisfies the point definition identified as display data and isassociated with a second device of the same type of building equipment,wherein the point definition comprises a search criterion foridentifying the data point associated with the second device, the searchcriterion comprising the abstraction of the text string extracted from acorresponding data point associated with the archetypal device;automatically mapping the identified data point to a display object;generating a user interface for display on a client device, the userinterface comprising a display of the data point mapped to the displayobject; and using the display object to monitor and control the seconddevice to affect a variable state or condition within a building.